Bug 1935855

Summary: [sig-node] pods should never transition back to pending
Product: OpenShift Container Platform Reporter: Varsha <vnarsing>
Component: NodeAssignee: Ryan Phillips <rphillips>
Node sub component: Kubelet QA Contact: Sunil Choudhary <schoudha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aos-bugs, eparis, jokerman, mfojtik, sponnaga, sttts
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
[sig-node] pods should never transition back to pending
Last Closed: 2021-03-12 15:34:13 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 Varsha 2021-03-05 17:20:01 UTC
test:
[sig-node] pods should never transition back to pending 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-node%5C%5D+pods+should+never+transition+back+to+pending

Link to logs:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-gcp-upgrade/1367835027068424192

FIXME: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

FIXME: Provide a snippet of the test failure or error from the job log

A similar bug against 4.6 - https://bugzilla.redhat.com/show_bug.cgi?id=1886920)

Comment 1 Varsha 2021-03-05 17:22:28 UTC
There is already a similar bug created against 4.6 - https://bugzilla.redhat.com/show_bug.cgi?id=1882750
Since I started seeing this in 4.8, I have created a bug. Please feel free to close this as a dup if this is currently being worked on and will solve the errors against 4.8 release too.

Comment 7 Ryan Phillips 2021-03-12 15:34:13 UTC

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