Bug 1951617

Summary: [sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes
Product: OpenShift Container Platform Reporter: Lakshmi Ravichandran <lakshmi.ravichandran1>
Component: OLMAssignee: Kevin Rizza <krizza>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: low    
Priority: low CC: anbhatta, dmistry, dsover
Version: 4.8   
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-21 21:05:00 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 Lakshmi Ravichandran 2021-04-20 14:56:58 UTC 
Description of problem:
The test "[sig-arch] Managed cluster should have no crashlooping pods in core namespaces over four minutes [Suite:openshift/conformance/parallel]"

fails on 4.8 CI jobs for s390x. 

It has been observed to fail over the CI runs:
1. 04/20 - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-remote-libvirt-s390x-4.8/1384295824116158464

2. 04/15 -  https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-remote-libvirt-s390x-4.8/1382484001675022336

3. 04/12 - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-remote-libvirt-s390x-4.8/1381577904302854144


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

How reproducible:
please, refer to the CI jobs in the above links

Steps to Reproduce:
please, refer to the CI jobs in the above links

Actual results:
the test fails on 4.8 CI jobs for s390x

Expected results:
the test should pass in CI
e.g: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-remote-libvirt-s390x-4.8/1382846217062453248

Additional info:
Comment 1 Daniel Sover 2021-04-20 17:04:41 UTC 
The error is "Pod openshift-marketplace/certified-operators-ptnxm is not healthy: container registry-server exited with non-zero exit code"

How often does this error occur? Is it a flake, or are all s390x builds broken? Setting to low priority for now.
Comment 2 Deep Mistry 2021-04-20 17:53:41 UTC 

https://search.ci.openshift.org/?search=container+registry-server+exited+with+non-zero+exit+code&maxAge=168h&context=0&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Flaky for s390x
Comment 3 Anik 2021-04-21 21:05:00 UTC 
Looks like this is duplicate of #1949991

Please re-open the bug if you think there's something different to consider for this bz.

*** This bug has been marked as a duplicate of bug 1949991 ***
Comment 4 Lakshmi Ravichandran 2021-04-30 10:06:13 UTC 
following on the bug 1949991 for resolution.