]> git.apps.os.sepia.ceph.com Git - ceph-ansible.git/commit
podman: always remove container on start
authorDimitri Savineau <dsavinea@redhat.com>
Tue, 21 Jul 2020 13:32:50 +0000 (09:32 -0400)
committerGuillaume Abrioux <gabrioux@redhat.com>
Thu, 23 Jul 2020 15:00:38 +0000 (17:00 +0200)
commit47b7c00287f310ab38e442ba2a147e9f7faab1ee
tree770b8907b48111cee2cab55b7636b3d807c87284
parent44caa062b7ada6f4d992d61632e624bb0f757bcd
podman: always remove container on start

In case of failure, the systemd ExecStop isn't executed so the container
isn't removed. After a reboot of a failed node, the container doesn't
start because the old container is still present in created state.
We should always try to remove the container in ExecStartPre for this
situation.
A normal reboot doesn't trigger this issue and this also doesn't affect
nodes running containers via docker.
This behaviour was introduced by d43769d.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1858865
Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
14 files changed:
roles/ceph-grafana/templates/grafana-server.service.j2
roles/ceph-iscsi-gw/templates/rbd-target-api.service.j2
roles/ceph-iscsi-gw/templates/rbd-target-gw.service.j2
roles/ceph-iscsi-gw/templates/tcmu-runner.service.j2
roles/ceph-mds/templates/ceph-mds.service.j2
roles/ceph-mgr/templates/ceph-mgr.service.j2
roles/ceph-mon/templates/ceph-mon.service.j2
roles/ceph-nfs/templates/ceph-nfs.service.j2
roles/ceph-node-exporter/templates/node_exporter.service.j2
roles/ceph-osd/templates/ceph-osd.service.j2
roles/ceph-prometheus/templates/alertmanager.service.j2
roles/ceph-prometheus/templates/prometheus.service.j2
roles/ceph-rbd-mirror/templates/ceph-rbd-mirror.service.j2
roles/ceph-rgw/templates/ceph-radosgw.service.j2