Bug 2005108 - removing and recreating static pod manifest leaves pod in error state
Summary: removing and recreating static pod manifest leaves pod in error state
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.9.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On: 1999133
Blocks: 1981999
TreeView+ depends on / blocked
 
Reported: 2021-09-16 19:21 UTC by OpenShift BugZilla Robot
Modified: 2021-10-18 17:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 17:51:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 964 0 None Merged [release-4.9] BUG 2005108: UPSTREAM: 104847: Handle UID reuse in pod worker 2021-09-17 18:55:18 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:52:07 UTC

Comment 3 Sunil Choudhary 2021-09-21 15:30:52 UTC 
Verified on 4.9.0-0.nightly-2021-09-20-203004

Created a static pod yaml in /etc/kubernetes/manifests on the node, deleted and recreated the pod.

sh-4.4# pwd
/etc/kubernetes/manifests

sh-4.4# cat mypod.yaml 

kind: Pod
apiVersion: v1
metadata:
  name: mypod
spec:
  terminationGracePeriodSeconds: 1
  containers:
  - name: busybox
    image: busybox
    command: ["sh", "-c", "echo $RANDOM; sleep 100000"]


$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2021-09-20-203004   True        False         175m    Cluster version is 4.9.0-0.nightly-2021-09-20-203004

$ oc get pods -o wide -n default
NAME                                               READY   STATUS    RESTARTS   AGE     IP            NODE                                         NOMINATED NODE   READINESS GATES
ip-10-0-158-20ap-south-1computeinternal-debug      1/1     Running   0          4m13s   10.0.158.20   ip-10-0-158-20.ap-south-1.compute.internal   <none>           <none>
mypod-ip-10-0-158-20.ap-south-1.compute.internal   1/1     Running   0          35s     10.129.2.59   ip-10-0-158-20.ap-south-1.compute.internal   <none>           <none>

$ oc get pods -o wide -n default
NAME                                            READY   STATUS    RESTARTS   AGE     IP            NODE                                         NOMINATED NODE   READINESS GATES
ip-10-0-158-20ap-south-1computeinternal-debug   1/1     Running   0          5m53s   10.0.158.20   ip-10-0-158-20.ap-south-1.compute.internal   <none>           <none>

$ oc get pods -o wide -n default
NAME                                               READY   STATUS    RESTARTS      AGE     IP            NODE                                         NOMINATED NODE   READINESS GATES
ip-10-0-158-20ap-south-1computeinternal-debug      1/1     Running   0             6m37s   10.0.158.20   ip-10-0-158-20.ap-south-1.compute.internal   <none>           <none>
mypod-ip-10-0-158-20.ap-south-1.compute.internal   1/1     Running   1 (57s ago)   33s     10.129.2.60   ip-10-0-158-20.ap-south-1.compute.internal   <none>           <none>
Comment 6 errata-xmlrpc 2021-10-18 17:51:49 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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-2021:3759
Note You need to log in before you can comment on or make changes to this bug.