systemd: handle running container without systemd unit
MariaDB bootstrap has a phase where the first MariaDB container is running with Galera bootstrap - after a check that WSREP is synced is successful - we restart the container. The bootstrap container is named mariadb and running with docker_restart_policy: "no" - the restarted container should be running in systemd. Before this patch the code created a systemd unit but it was initially stopped - so stopping was always a success - and the container would be killed with SIGKILL on removal (which obviously breaks MariaDB). This patch also improves docker/systemd stops by waiting for real unit/container stop and adds failing CI for containers that are killed with signal 9. Closes-Bug: #2029613 Change-Id: I0a03e509ce228a50e081fcab44d2b4831251190c
Showing
- ansible/module_utils/kolla_docker_worker.py 3 additions, 4 deletionsansible/module_utils/kolla_docker_worker.py
- ansible/module_utils/kolla_systemd_worker.py 9 additions, 4 deletionsansible/module_utils/kolla_systemd_worker.py
- tests/check-logs.sh 8 additions, 0 deletionstests/check-logs.sh
- tests/kolla_docker_tests/test_docker_worker.py 1 addition, 0 deletionstests/kolla_docker_tests/test_docker_worker.py
Please register or sign in to comment