Red Hat Bugzilla – Bug 1431782
kubelet status manager does not always report correct status
Last modified: 2017-07-24 10:11 EDT
Description of problem: This is a tracking bug to handle the back-port of the following: https://github.com/kubernetes/kubernetes/pull/41436 In TerminatePod, we previously pass pod.Status to updateStatusInternal. This is a bug, since it is the original status that we are given. Not only does it skip updates made to container statuses, but in some cases it reverted the pod's status to an earlier version, since it was being passed a stale status initially. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
1.5 PR posted for Origin here: https://github.com/openshift/origin/pull/13377
Derek, could you provide reproduce steps? Thanks.
There is no clear reproduction procedure to follow for this. We just need to ensure that the basic lifecycle of a pod continues to function when verifying this fix.
Verified on openshift v3.5.0.54. No issue found. Fixed. Steps: try pods with status runing, completed and Error, pod/container state is correct. 1. oc create -f https://raw.githubusercontent.com/mdshuai/testfile-openshift/master/k8s/terminatedpods/emtydir-host.yaml 2. oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/pods/graceful-delete/default.json 3. oc get pod -o yaml, and check all pod/container state
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-2017:0884