That doesn't seem to be sufficient - still fails in https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-okd-4.6-e2e-aws/1357601385683619840 (but I can't figure out why, the output looks fine to me)
Curious Vadim ... maybe some whitespace issues? I'll boot up a 4.6 OKD cluster via https://origin-release.apps.ci.l2s4.p1.openshiftapps.com/#4.6.0-0.okd and try running the test manually.
yeah the tests pass for me Vadim against okd-2021-01-29-161622 An I just looked at periodic-ci-openshift-release-master-okd-4.6-e2e-aws via https://prow.ci.openshift.org/?job=periodic-ci-openshift-release-master-okd-4.6-e2e-aws and I see a green test now at https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-okd-4.6-e2e-aws/1357728529000697856 Perhaps there was a delay in the latest openshift/origin level getting used in the test run. Moving this back to modified
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 (OpenShift Container Platform 4.6.17 bug fix 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/RHBA-2021:0424