Bug 1726934
| Summary: | Pod phase seems to break its invariants again | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Tomáš Nožička <tnozicka> |
| Component: | Node | Assignee: | Ryan Phillips <rphillips> |
| Status: | CLOSED DUPLICATE | QA Contact: | Sunil Choudhary <schoudha> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.z | CC: | aos-bugs, ccoleman, erich, gblomqui, jokerman, mmccomas, pthomas, rgudimet, sttts |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-06 21:07:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tomáš Nožička
2019-07-04 06:19:25 UTC
I do wonder if this is happening when the node reboots. When the kubelet goes down on a reboot, the pods stay running and there is nothing to report to the apiserver when the pods go down on node shutdown. Maybe the kubelet is coming back up, gets the list of pods, and moves from Running->Pending since the pod is indeed not running. Then attempts to start it and then it transitions back to running. I'm not entirely sure that this is illegal in that case. A quick check shows that this definitely doesn't happen every time. I rebooted a node and did a watch on pods, when the kubelet came back, all the pods statuses were updated once but the state remained Running. also seen in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.2/343 Aug 12 09:45:18.278 W ns/openshift-machine-config-operator pod/machine-config-daemon-skpkw node/ip-10-0-140-14.ec2.internal invariant violation (bug): pod should not transition Running->Pending even when terminated I tried to recreate this a few ways without success. The pod lifecycle has never been formalized, but is seems that Running -> Pending should not be allow. However, it is not explicitly disallowed and seems like it wouldn't cause an issue, unlike the Failed -> Succeeded transitions we've seen in the past. *** This bug has been marked as a duplicate of bug 1810652 *** |