Accept exit status 142 for containers
Bug #1922179 reported by
Cédric Jeanneret
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
Medium
|
Cédric Jeanneret | ||
Bug Description
In the same way we accepted 137 and 143, we also need to accept the 142 (SIGALRM) code.
It affects python-paunch for >= stable/ussuri, and tripleo-ansible for newer releases.
Revision history for this message
| Cédric Jeanneret (cjeanner) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/paunch 7.0.4 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-ansible 1.5.3 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-ansible 3.1.0 | #4 |
| Changed in tripleo: | |
| milestone: | wallaby-rc1 → xena-1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-ansible 2.3.0 | #5 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/paunch 5.5.1 | #6 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-ansible 0.8.0 | #7 |
| Changed in tripleo: | |
| milestone: | xena-1 → xena-2 |
| Changed in tripleo: | |
| milestone: | xena-2 → xena-3 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
https:/
https:/