Description of problem: The recently added TestIngressStatus test fails on Azure, causing the e2e-azure-operator CI jobs in the cluster-ingress-operator repository to fail consistently. OpenShift release version: The test was added in OpenShift 4.9. Cluster Platform: Azure. How reproducible: Consistently. Steps to Reproduce (in detail): 1. Run the e2e-azure-operator CI job. Actual results: The e2e-azure-operator CI job consistently fails. See https://github.com/openshift/cluster-ingress-operator/pull/659#issuecomment-943881965 for an example failure. Expected results: The e2e-azure-operator CI job should pass. Impact of the problem: The e2e-azure-operator CI job is broken, which prevents us from using it to validate PRs on Azure. Additional info: The new test was introduced in https://github.com/openshift/cluster-ingress-operator/pull/641. A fix was posted in https://github.com/openshift/cluster-ingress-operator/pull/662 and has already merged into the master branch. I am filing this Bugzilla report so that we will be able to link the PR to a Bugzilla report and then backport the fix to the release-4.9 branch.
the test e2e-azure-operator looks good, moving to verified.
Changes were requested on the release-4.9 backport[1], so I am making those changes on the main branch and will open a new backport PR that incorporates those changes. 1. https://github.com/openshift/cluster-ingress-operator/pull/664#pullrequestreview-793432926
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.10.3 security 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-2022:0056