Bug 1642589 - Uninstall playbook don't remove or stop any static pods at container runtime
Summary: Uninstall playbook don't remove or stop any static pods at container runtime
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.11.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Jeremiah Stuever
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-24 18:03 UTC by German Montalvo
Modified: 2019-10-23 02:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-11 05:38:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3964391 0 Supportability None Uninstall playbook don't remove or stop any static pods at container runtime 2019-03-05 18:03:53 UTC
Red Hat Product Errata RHBA-2019:0636 0 None None None 2019-04-11 05:38:38 UTC

Description German Montalvo 2018-10-24 18:03:33 UTC
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

Comment 2 Scott Dodson 2018-10-26 19:35:56 UTC
Workaround, reboot the host and they shouldn't come back.

Comment 3 Jeremiah Stuever 2019-02-21 19:18:14 UTC
https://github.com/openshift/openshift-ansible/pull/11226

Comment 5 Qin Ping 2019-03-04 01:54:51 UTC
This PR is not contained in openshift-ansible-3.11.88

Comment 9 Xingxing Xia 2019-03-21 01:19:00 UTC
(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!

Comment 10 Qin Ping 2019-03-22 02:06:47 UTC
Verified with: openshift-ansible-3.11.98-1

Comment 12 errata-xmlrpc 2019-04-11 05:38:23 UTC
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


Note You need to log in before you can comment on or make changes to this bug.