Mariadb recovery fails if mariadb container does not exist
Bug #1907658 reported by
Mark Goddard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Fix Released
|
Medium
|
Unassigned | ||
| Train |
Fix Released
|
Medium
|
Unassigned | ||
| Ussuri |
Fix Released
|
Medium
|
Unassigned | ||
| Victoria |
Fix Released
|
Medium
|
Unassigned | ||
| Wallaby |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Mariadb recovery fails if a cluster has previously been deployed, but any of the mariadb containers do not exist.
Steps to reproduce
==================
* Deploy a mariadb galera cluster
* Remove the mariadb container from at least one host (docker rm -f mariadb)
* Run kolla-ansible mariadb_recovery
Expected results
================
The cluster is recovered, and a new container deployed where necessary.
Actual results
==============
The task 'Stop MariaDB containers' fails on any host where the container does not exist.
Environment
===========
Train, CentOS 8
| Changed in kolla-ansible: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 10.2.0 | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 11.0.0.0rc2 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 9.3.0 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 12.0.0.0rc1 | #4 |
To post a comment you must log in.
This issue was fixed in the openstack/