mirror of https://github.com/ceph/ceph-ansible.git
47b7c00287
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
|
||
|---|---|---|
| .github | ||
| contrib | ||
| docs | ||
| group_vars | ||
| infrastructure-playbooks | ||
| library | ||
| plugins | ||
| profiles | ||
| roles | ||
| tests | ||
| .gitignore | ||
| .mergify.yml | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README-MULTISITE.md | ||
| README.rst | ||
| Vagrantfile | ||
| ansible.cfg | ||
| ceph-ansible.spec.in | ||
| dashboard.yml | ||
| dummy-ansible-hosts | ||
| generate_group_vars_sample.sh | ||
| raw_install_python.yml | ||
| requirements.txt | ||
| rhcs_edits.txt | ||
| site-container.yml.sample | ||
| site.yml.sample | ||
| test.yml | ||
| tox-cephadm.ini | ||
| tox-docker2podman.ini | ||
| tox-external_clients.ini | ||
| tox-filestore_to_bluestore.ini | ||
| tox-podman.ini | ||
| tox-update.ini | ||
| tox.ini | ||
| vagrant_variables.yml.sample | ||
README.rst
ceph-ansible ============ Ansible playbooks for Ceph, the distributed filesystem. Please refer to our hosted documentation here: http://docs.ceph.com/ceph-ansible/master/ You can view documentation for our ``stable-*`` branches by substituting ``master`` in the link above for the name of the branch. For example: http://docs.ceph.com/ceph-ansible/stable-3.0/