Bug 1771172
| Summary: | [Multi Arch] cri-o rejects clone calls on s390x | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | David Benoit <dbenoit> | |
| Component: | Node | Assignee: | Ryan Phillips <rphillips> | |
| Node sub component: | CRI-O | QA Contact: | Jeremy Poulin <jpoulin> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | unspecified | CC: | adam.kaplan, aos-bugs, dgilmore, eparis, Holger.Wolf, imcleod, jokerman, lsm5, miabbott, psundara, smilner, weinliu, wzheng, xtian | |
| Version: | 4.2.z | Flags: | psundara:
needinfo-
psundara: needinfo- |
|
| Target Milestone: | --- | |||
| Target Release: | 4.3.0 | |||
| Hardware: | s390x | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | cri-o-1.14.11-0.24.dev.rhaos4.2.gitc41de67.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1794122 1794191 (view as bug list) | Environment: | ||
| Last Closed: | 2020-01-23 11:12:18 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: | 1794122, 1794191 | |||
|
Description
David Benoit
2019-11-11 22:11:34 UTC
Edit: Affects version 1.14.11. Yes, this can be closed. It has been verified. Latest RHCOS 4.2 for s390x from ART pipeline includes the fixed package: ``` $ curl -Ls https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.2-s390x/42s390x.81.20191218.0/commitmeta.json | jq '.["rpmostree.rpmdb.pkglist"][] | select(. [0] == "cri-o")' [ "cri-o", "0", "1.14.11", "0.24.dev.rhaos4.2.gitc41de67.el8", "s390x" ] ``` Moving to VERIFIED 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 |