Ship a newer ostree in 4.2.z to enable s390x.
So far, we haven't really had a formal process for shipping host updates on z streams. Basically we don't do any new builds for "CoreOS parts" (ignition, ostree) and just take base RHEL updates which is mostly security.
Let's use this bug to track signoff for shipping a new ostree in 4.2.z to enable s390x.
A lot of patches went in; it'd be possible to backport but in practice ostree has only merged quite safe changes, we have CI etc. I think it's better from a testing standpoint to ship a new upstream release.
Assuming new tag 2019.5 by Colin yesterday, then I guess we are good with this one. https://github.com/ostreedev/ostree/releases/tag/v2019.5
`ostree-2019.5-1.el8.s390x.rpm` has been tagged into the RHAOS 4.2 puddle
Verified with registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-11-26-164052
$ oc image info --output json $(oc adm release info -a ~/openshift-cluster-installs/all-the-pull-secrets.json --image-for=machine-os-content registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-11-26-164052) | jq .config.config.Labels.version
$ curl -Ls https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.2/42.81.20191126.0/commitmeta.json | jq '.["rpmostree.rpmdb.pkglist"] | select(. == "ostree")'
(While this is for the x86_64 arch, the s390x version is included in the same puddle used to build the x86_64 version)
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.