Bug 2009092 - Kubelet logging "Pod attempted illegal phase transition"
Summary: Kubelet logging "Pod attempted illegal phase transition"
Keywords:
Status: CLOSED DUPLICATE of bug 2011513
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Elana Hashman
QA Contact: Weinan Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-29 23:05 UTC by Elana Hashman
Modified: 2021-10-13 14:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-13 14:32:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Elana Hashman 2021-09-29 23:05:29 UTC
Description of problem:

In a couple of 4.9 bugs, we've seen instances where the kubelet is logging that a pod attempted an illegal phase transition, e.g.

https://bugzilla.redhat.com/show_bug.cgi?id=1998193#c16
https://bugzilla.redhat.com/show_bug.cgi?id=1997478#c25

I suspect this may be related to the 4.9 pod lifecycle refactor, as this doesn't appear to have been present in earlier versions.

This log message is invoked here: https://github.com/openshift/kubernetes/blob/f181eb2582e1649676395f25710c14b427b3369c/pkg/kubelet/kubelet_pods.go#L1480-L1484

It's only possible when a terminal pod (failed or succeeded) attempts a phase transition.


Version-Release number of selected component (if applicable):

OpenShift 4.9

How reproducible:

Unclear

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Elana Hashman 2021-10-05 22:26:00 UTC
We saw that some Pods were returning to Running or Pending in https://github.com/kubernetes/kubernetes/issues/105358

Let's see if openshift/kubernetes#999 fixes this.

Comment 2 Ryan Phillips 2021-10-13 14:32:03 UTC

*** This bug has been marked as a duplicate of bug 2011513 ***


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