[python-tripleoclient] overcloud deployment fails, but exits 0
Bug #1631177 reported by
wes hayutin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Adriano Petrich | ||
| tripleo-quickstart |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
The overcloud deployment fails however for what ever reason heat does not post a "CREATE_FAILED" statement that would trigger oooq to further debug the failure.
This can be fixed by adjusting the regex that detects the failure [1]
Revision history for this message
| John Trowbridge (trown) wrote | #1 |
| Changed in tripleo-quickstart: | |
| status: | New → Invalid |
| summary: |
- overcloud deployment fails, but oooq does not detect the failure + [python-tripleoclient] overcloud deployment fails, but exits 0 |
| Changed in tripleo: | |
| importance: | Undecided → High |
| milestone: | none → ocata-1 |
| status: | New → Triaged |
| Changed in tripleo: | |
| milestone: | ocata-1 → ocata-2 |
| tags: | added: low-hanging-fruit |
| tags: | added: tripleoclient |
| Changed in tripleo: | |
| assignee: | nobody → Adriano Petrich (apetrich) |
Revision history for this message
| Adriano Petrich (apetrich) wrote | #2 |
Revision history for this message
| wes hayutin (weshayutin) wrote | #3 |
| Changed in tripleo: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This was originally filed as a tripleo-quickstart bug, but we should not need regex magic to detect a deployment failure. Instead the `openstack overcloud deploy` command should exit with non-zero exit code if it was not successful.