Capomastro's Mojo spec should have a precheck phase

Bug #1421658 reported by Caio Begotti
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Caio Begotti

Bug Description

In environments where it is quite slow to test and develop the service spec (e.g. Canonistack, which takes about 2h for a deployment) the whole Mojo run can fail miserably after a long hour because we missed a tiny config step.

I would expect to have a <stagename>/precheck script to check that the Nova configuration (to ensure all OS_* variables are set), the Jenkins volume is set up, the secrets and mapping files are in place etc. This way we can abort the run right away before noticing something simple was missed by accident, thus making the service spec more robust and stable.

Revision history for this message
Daniel Manrique (roadmr) wrote :

+10000. Even just the collect step takes about 10 minutes to run (bzr is damn slow). So doing this as a script step *before* anything else may be a good idea. If not, perhaps right after the secrets phase would be good enough.

Changed in capomastro:
status: New → Triaged
importance: Undecided → High
milestone: none → 2015-04
Caio Begotti (caio1982)
Changed in capomastro:
assignee: nobody → Caio Begotti (caio1982)
Caio Begotti (caio1982)
Changed in capomastro:
status: Triaged → Fix Committed
Daniel Manrique (roadmr)
Changed in capomastro:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.