Description of problem: cri-o rejects clone calls on s390x Version-Release number of selected component (if applicable): 1.14.13 How reproducible: Always Steps to Reproduce: 1. Run kubernetes on s390x using cri-o and ose-pod instead of kube pause container. Actual results: Clone call in golang runtime startup is rejected by seccomp. Expected results: ose-pod works as a drop-in replacement for kube pause. Additional info: Patch submitted upstream, awaiting review. https://github.com/opencontainers/runtime-tools/issues/699
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