Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
We cannot stop/kill the containers specifically the ovs pods on the masters having the docker-1.13.1-108.git4ef4b30.el7.x86_64 installed.
Version-Release number of selected component (if applicable):
docker-1.13.1-108.git4ef4b30.el7.x86_64
How reproducible:
Fully reproducible
Pod goes into "Terminating" state and the docker ps shows it running. It works completely well with 1.13.1-104 version.
# oc get po -o wide -w
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE
ovs-55ktk 1/1 Running 7 29d 10.74.176.108 master-2.sank311.lab.pnq2.cee.redhat.com <none>
ovs-6gvrn 1/1 Running 0 29d 10.74.176.98 infra-1.sank311.lab.pnq2.cee.redhat.com <none>
ovs-97tzz 1/1 Running 0 29d 10.74.176.117 infra-0.sank311.lab.pnq2.cee.redhat.com <none>
ovs-c74hl 1/1 Running 3 8d 10.74.176.97 node-0.sank311.lab.pnq2.cee.redhat.com <none>
ovs-m9qnv 1/1 Terminating 3 29d 10.74.176.83 master-0.sank311.lab.pnq2.cee.redhat.com <none>
[root@master-0 ~]# docker ps | grep ovs
c9ca58ecc9e3 090ef2f67ef6 "/bin/bash -c '#!/..." 8 minutes ago Up 8 minutes k8s_openvswitch_ovs-m9qnv_openshift-sdn_45bf0b41-2b12-11ea-a3c4-fa163ea08191_3
[root@master-0 ~]# docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-108.git4ef4b30.el7.x86_64
Go version: go1.10.3
Git commit: 4ef4b30/1.13.1
Built: Fri Dec 13 01:48:25 2019
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-108.git4ef4b30.el7.x86_64
Go version: go1.10.3
Git commit: 4ef4b30/1.13.1
Built: Fri Dec 13 01:48:25 2019
OS/Arch: linux/amd64
Experimental: false
Actual results:
Cannot stop ovs pods
Expected results:
Should able to stop ovs pods
Additional info:
May be it is related to the regression in the runc code of docker-1.13.1-108.git4ef4b30.el7.x86_64
Related bugzillas : https://bugzilla.redhat.com/show_bug.cgi?id=1791870https://bugzilla.redhat.com/show_bug.cgi?id=1793486
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/RHSA-2020:1234