kolla-ansible/bug-1907658-a24ddc45f63893b5.yaml at 3b824a0a12ff51fdfaac17893bb1e591307c904d - kolla-ansible - OpenDev: Free Software Needs Free Tools

openstack/kolla-ansible

Mark Goddard f903d774af Fix mariadb_recovery when mariadb container is missing

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.

Solution
========

This change fixes the issue by using the 'ignore_missing' flag for kolla_docker
with the stop_container action. This means the task does not fail when the
container does not exist. It is also necessary to swap some 'docker cp'
commands for 'cp' on the host, using the path to the volume.

Closes-Bug: #1907658

Change-Id: Ibd4a6adeb8443e12c45cbab65f501392ffb16fc7

2020-12-10 12:27:25 +00:00

7 lines

223 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     Fixes an issue with ``kolla-ansible mariadb_recovery`` when the ``mariadb``
     container does not exist on one or more hosts. `LP#1907658
     <https://bugs.launchpad.net/kolla-ansible/+bug/1907658>`__