ironic-conductor should not exit 0 on failure
Bug #1650347 reported by
Yuriy Zveryanskyy
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Fix Released
|
Medium
|
Joanna Taryma | ||
Bug Description
If conductor service fails due to fatal error (for example corrupted DB) it returns exit code 0 (success). Example of error log: http://
| summary: |
- Wrong exit code from conductor process + ironic-conductor should not exit 0 on failure |
| Changed in ironic: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in ironic: | |
| assignee: | nobody → Joanna Taryma (jtaryma) |
Revision history for this message
| Joanna Taryma (jtaryma) wrote | #1 |
| Changed in ironic: | |
| status: | Triaged → Incomplete |
Revision history for this message
| Dmitry Tantsur (divius) wrote | #2 |
| Changed in ironic: | |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
Yuriy, could you please provide me with conductor startup command? I have a suspicion that zero exit code is actually caused by piping in the startup command.
Kind regards,
Joanna