add breakup points on grenade.sh to help debug
Bug #1182872 reported by
Adalberto Medeiros
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grenade |
Invalid
|
Undecided
|
Adalberto Medeiros | ||
Bug Description
When running grenade.sh, it can break on some points during base setup, like on stack.sh, javelin, downloading the cirros image or during devstack exercises.
However, when running steps for the target release, breakups can be fixed running the individual upgrade-* scripts, rerunning stack.sh and exercise.sh on the target devstack.
Thus, in order to gain more granularity in the base steps, I propose here to break the grenade script in more parts, to help debugging.
This would be useful to have a start point after running the stack.sh, another just for caching the images and finally, one for setup javelin.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to grenade (master) | #1 |
| Changed in grenade: | |
| assignee: | nobody → Adalberto Medeiros (adalbas) |
| status: | New → In Progress |
| Changed in grenade: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/