Description of problem: Hi there, After trigger uninstall playbook on openshift 3.11 with cri-o runtime and trigger an uninstall playbook we realize that cri-o containers are not being deleted: Version-Release number of the following components: rpm -q openshift-ansible openshift-ansible-3.11.16-1.git.0.4ac6f81.el7.noarch rpm -q ansible ansible-2.6.5-1.el7ae.noarch ansible --version ansible 2.6.5 config file = /etc/ansible/ansible.cfg configured module search path = [u'/home/germanm/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, May 31 2018, 09:41:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)] How reproducible: Steps to Reproduce: 1. Deploy openshift 3.11.16 with openshift_use_crio=true 2. Uninstall using oficial playbook 3. crictl ps and you will see: 1 Actual results: after uninstall there shouldn't by any remaining container, but: crictl ps CONTAINER ID IMAGE CREATED STATE NAME ATTEMPT 93b1b9fc1c320 1f23828b535ba974d9a4b692cb4f8f42cb3482dd524e38aa90ee5fd1120b6192 5 hours ago Running api 30 4c69a53df37f5 1f23828b535ba974d9a4b692cb4f8f42cb3482dd524e38aa90ee5fd1120b6192 8 hours ago Running controllers Expected results: No remaining containers active (running or existing) Additional info: Please attach logs from ansible-playbook with the -vvv flag
Workaround, reboot the host and they shouldn't come back.
https://github.com/openshift/openshift-ansible/pull/11226
This PR is not contained in openshift-ansible-3.11.88
(In reply to Qin Ping from comment #5) > This PR is not contained in openshift-ansible-3.11.88 Qin Ping, PR merged in version >= openshift-ansible-3.11.90, could you continue helping verify it when available? Thank you!
Verified with: openshift-ansible-3.11.98-1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0636