Description of problem: Bug 1916897 has added a test which ensures /run is writable during the builds. It expects `rhsm` to contain subscription details from the host. This test fails on OKD payloads, as FCOS doesn't have subscription information.
Hi @gabe still met error as follow: https://search.ci.openshift.org/?search=%5C%5Bsig-builds%5C%5D%5C%5BFeature%3ABuilds%5C%5D+verify+%2Frun+filesystem+contents++do+not+have+unexpected+content+using+a+simple+Docker+Strategy+Build&maxAge=6h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job Maybe wait the bug (https://bugzilla.redhat.com/show_bug.cgi?id=1924128) verify together.
I'm fine either way @Wen, but one could argue you could go ahead and mark this verified so we can speed up the clean up on your query. Going through the hits on your query, one can categorize in short order that the failures there were 1) On 4.6 OKD. We of course cannot port this fix to 4.6 until after this BZ is verified. The majority of hits I got from your query were 4.6 OKD. failures for the jobs rehearse-12691-pull-ci-operator-framework-operator-marketplace-release-4.6-okd-e2e-aws periodic-ci-openshift-release-master-okd-4.6-e2e-aws promote-release-openshift-okd-machine-os-content-e2e-aws-4.7 - I believe this was just showing the delay in getting a payload with my fix .... the last 2 runs at https://prow.ci.openshift.org/job-history/origin-ci-test/logs/promote-release-openshift-okd-machine-os-content-e2e-aws-4.7 are clean If we verified this, I could start the backport of this BZ's changes to 4.6 and clean those up faster. 2) or the job name specifically mentions the rhel7 worker node item noted in https://bugzilla.redhat.com/show_bug.cgi?id=1924128 periodic-ci-openshift-release-master-ocp-4.7-e2e-aws-workers-rhel7 pull-ci-openshift-machine-config-operator-master-e2e-aws-workers-rhel7 periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-workers-rhel7
landed in https://amd64.origin.releases.ci.openshift.org/releasestream/4.7.0-0.okd/release/4.7.0-0.okd-2021-02-03-132253, no longer failing in AWS tests there
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633