Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1867780

Summary: [sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes: openshift-infra/recycler-for-nfs errors
Product: OpenShift Container Platform Reporter: Yu Qi Zhang <jerzhang>
Component: StorageAssignee: Tomas Smetana <tsmetana>
Status: CLOSED DUPLICATE QA Contact: Qin Ping <piqin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
[sig-apps][Feature:DeploymentConfig] deploymentconfigs with test deployments should run a deployment to completion and then scale to zero
Last Closed: 2020-08-28 13:27: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 Yu Qi Zhang 2020-08-10 18:18:26 UTC 
test:
Managed cluster should have no crashlooping pods in core namespaces over four minutes [Suite:openshift/conformance/parallel]

is failing frequently in CI in 4.6. Although this test fails quite a bit for different reasons as it tracks many pods, a relatively common failure is that something went wrong for the recycler-for-nfs pod, recent examples:

https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.6/1292725766252924928
https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.6/1292859164099350528
https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.6/1292208595986812928
https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.6/1291677336395059200

See also search:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=4.6&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-arch%5C%5D+Managed+cluster+should+have+no+crashlooping+pods+in+core+namespaces+over+four+minutes
Comment 2 Tomas Smetana 2020-08-21 07:40:50 UTC 
I went through the logs... There's just timeouts but no visible errors or breakages usually. "UpcomingSprint": I keep digging into this.
Comment 3 Tomas Smetana 2020-08-28 13:27:13 UTC 

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