Component Readiness has found a potential regression in the following test:

[bz-Routing] clusteroperator/ingress should not change condition/Available

Probability of significant regression: 97.63%

Sample (being evaluated) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-09-09T23:59:59Z
Success Rate: 89.29%
Successes: 25
Failures: 3
Flakes: 0

Base (historical) Release: 4.16
Start Time: 2024-05-28T00:00:00Z
End Time: 2024-06-27T23:59:59Z
Success Rate: 100.00%
Successes: 67
Failures: 0
Flakes: 0

View the test details report at https://sippy.dptools.openshift.org/sippy-ng/component_readiness/test_details?Aggregation=none&Architecture=amd64&Architecture=amd64&FeatureSet=default&FeatureSet=default&Installer=upi&Installer=upi&Network=ovn&Network=ovn&NetworkAccess=default&Platform=vsphere&Platform=vsphere&Scheduler=default&SecurityMode=default&Suite=serial&Suite=serial&Topology=ha&Topology=ha&Upgrade=none&Upgrade=none&baseEndTime=2024-06-27%2023%3A59%3A59&baseRelease=4.16&baseStartTime=2024-05-28%2000%3A00%3A00&capability=Operator&columnGroupBy=Architecture%2CNetwork%2CPlatform&component=Networking%20%2F%20router&confidence=95&dbGroupBy=Platform%2CArchitecture%2CNetwork%2CTopology%2CFeatureSet%2CUpgrade%2CSuite%2CInstaller&environment=amd64%20default%20upi%20ovn%20vsphere%20serial%20ha%20none&ignoreDisruption=true&ignoreMissing=false&includeVariant=Architecture%3Aamd64&includeVariant=FeatureSet%3Adefault&includeVariant=Installer%3Aipi&includeVariant=Installer%3Aupi&includeVariant=Owner%3Aeng&includeVariant=Platform%3Aaws&includeVariant=Platform%3Aazure&includeVariant=Platform%3Agcp&includeVariant=Platform%3Ametal&includeVariant=Platform%3Avsphere&includeVariant=Topology%3Aha&minFail=3&pity=5&sampleEndTime=2024-09-09%2023%3A59%3A59&sampleRelease=4.17&sampleStartTime=2024-09-01%2000%3A00%3A00&testId=openshift-tests%3Ab690e68fb6372a8924d84a0d6aa2f552&testName=%5Bbz-Routing%5D%20clusteroperator%2Fingress%20should%20not%20change%20condition%2FAvailable

It is worth mentioning that in two of the three failures, ingress operator went available=false at the same time image registry went available=false. This is one example.

Team can investigate, and if legit reason exists, please create an exception with origin and address it at proper time: https://github.com/openshift/origin/blob/4557bdcecc10d9fa84188c1e9a36b1d7d162c393/pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go#L90

Since this is appearing on component readiness dashboard and the management depends on a green dashboard to make release decisions, please give the initial investigation a high priority. If an exception is needed, please contact TRT team to triage the issue.