mistral-db-manage should have a different return code on partial failure
Bug #1689823 reported by
Dougal Matthews
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
The mistral-db-manage command will return as if there is no problems even if some of the actions failed to load. This makes it very hard to detect errors with tools like ansible or puppet.
For example, if an openstack action fails to load, it should not report that everything is super.
Recently a TripleO issue couldn't be found easily because the command didn't admit to any problems.
| description: | updated |
| Changed in mistral: | |
| assignee: | nobody → Toure Dunnon (toure) |
Revision history for this message
| Toure Dunnon (toure) wrote | #1 |
| Changed in mistral: | |
| milestone: | none → queens-1 |
| Changed in mistral: | |
| milestone: | queens-1 → queens-2 |
| Changed in mistral: | |
| milestone: | queens-2 → queens-3 |
| Changed in mistral: | |
| milestone: | queens-3 → rocky-1 |
| Changed in mistral: | |
| milestone: | rocky-1 → rocky-2 |
| status: | Confirmed → Triaged |
| Changed in mistral: | |
| assignee: | Toure Dunnon (toure) → nobody |
| milestone: | rocky-2 → none |
To post a comment you must log in.
Dougal is there an example of the command which was run, in regards to the TripleO instance?