Bug 1776043
| Summary: | make sure x86_64 samples are not installed on s390x clusters (initial 4.2.x targeted GA) | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> |
| Component: | Samples | Assignee: | Gabe Montero <gmontero> |
| Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.z | CC: | gmontero, xiuwang |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1775333 | Environment: | |
| Last Closed: | 2020-01-23 11:13:48 UTC | Type: | --- |
| 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: | 1775333 | ||
|
Comment 2
XiuJuan Wang
2019-11-25 02:56:28 UTC
This is actually no change from the jira issue, we just needed the bug in order to cherry-pick the change back to 4.2.z, so if you are comfortable w/ the validation you already did for the jira ticket you can simply move this to verified. As the test in the jira card, set samples operator to Removed, then change Architectures to s390x and state to Managed.
The clusteroperator openshift-samples show:
status:
conditions:
- lastTransitionTime: "2019-11-26T08:07:51Z"
reason: NonX86Platform
status: "True"
type: Available
- lastTransitionTime: "2019-11-26T08:07:51Z"
reason: NonX86Platform
status: "False"
type: Progressing
- lastTransitionTime: "2019-11-26T08:07:51Z"
reason: NonX86Platform
status: "False"
type: Degraded
And no x86_64 image installed under openshift project.
Verified with 4.3.0-0.nightly-2019-11-24-183610
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062 |