Bug 1847363

Summary: centos7 image missing
Product: OpenShift Container Platform Reporter: Rafael Fonseca <rdossant>
Component: Multi-ArchAssignee: Rafael Fonseca <rdossant>
Status: CLOSED UPSTREAM QA Contact: Barry Donahue <bdonahue>
Severity: low Docs Contact:
Priority: low    
Version: 4.3.zCC: danili, dslavens, yselkowi
Target Milestone: ---Keywords: TestOnly, UpcomingSprint
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard: multi-arch
Fixed In Version: 4.7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-04 15:42:32 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:
Bug Depends On:    
Bug Blocks: 1882454, 1905187    

Description Rafael Fonseca 2020-06-16 09:36:59 UTC
Description of problem: some tests fail because there is no centos7 image for s390x


Version-Release number of selected component (if applicable): 4.3, 4.4, 4.5


How reproducible: Always


Steps to Reproduce: Openshift CI


Additional info:

4.5 tests:
[sig-builds][Feature:Builds] Optimized image builds should succeed [Suite:openshift/conformance/parallel]
[sig-instrumentation] Prometheus when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early] [Suite:openshift/conformance/parallel]

Comment 2 Yaakov Selkowitz 2020-08-13 20:13:37 UTC
Can you point to the sources for the test in question?  Is modifying the test to use ubi8 an option?

Comment 4 Rafael Fonseca 2020-08-18 14:00:42 UTC
https://github.com/openshift/origin/pull/25014

Comment 8 Dan Li 2020-12-02 15:47:59 UTC
Adding UpcomingSprint tag as team will not have bandwidth to resolve this bug

Comment 9 Rafael Fonseca 2020-12-02 15:54:44 UTC
This upstream PR replaces some more centos usage https://github.com/openshift/origin/pull/25721

Comment 10 Rafael Fonseca 2020-12-04 15:42:32 UTC
Upstream PR #24887 linked in this issue resolves this problem as a side effect. PR #25721 is the current effort to backport those changes to ocp-4.6.

Since this issue affects only CI and I don't see backports being applied to any version older than 4.6, I'm closing this bug.