paunch doesn't properly stop when commands fail
Bug #1907833 reported by
Alex Schultz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Alex Schultz | ||
Bug Description
In paunch (<= ussuri), if stopping or removing a container fails, we don't properly halt the process which can result in systemctl files being removed but containers being left over. We should properly fail if stop or removing a container that exists and is running
Revision history for this message
| Alex Schultz (alex-schultz) wrote | #1 |
| Changed in tripleo: | |
| assignee: | nobody → Alex Schultz (alex-schultz) |
| status: | Triaged → In Progress |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/paunch 7.0.3 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/paunch 5.4.0 | #3 |
To post a comment you must log in.
https:/