Rolling-release for Swift does not work when deployed on different hosts
Bug #1899280 reported by
Benjamin FÜHRMANN
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Fix Released
|
Medium
|
Benjamin FÜHRMANN | ||
| Stein |
Triaged
|
Medium
|
Unassigned | ||
| Train |
Fix Released
|
Medium
|
Unassigned | ||
| Ussuri |
Fix Released
|
Medium
|
Unassigned | ||
| Victoria |
Fix Released
|
Medium
|
Benjamin FÜHRMANN | ||
Bug Description
When applying upgrade action on Swift, rolling restart does not stop containers on the right hosts if all Swift containers were not deployed on the same host. Ansible raises an error when trying to stop a non-deployed container.
Like reconfigure, we should execute action on Swift containers depending on the host there are deployed.
To reproduce issue, deploy Swift services on different hosts using dedicated Ansible groups (swift-
| Changed in kolla-ansible: | |
| assignee: | nobody → Benjamin FÜHRMANN (fuhrmannb) |
| status: | New → In Progress |
| Changed in kolla-ansible: | |
| importance: | Undecided → Medium |
| milestone: | none → 11.0.0 |
Revision history for this message
| Mark Goddard (mgoddard) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 10.2.0 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 11.0.0.0rc2 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 9.3.0 | #4 |
| Changed in kolla-ansible: | |
| milestone: | 11.0.0 → none |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 12.0.0.0rc1 | #5 |
To post a comment you must log in.
https:/