Issue 16258243: clusteroperator/console: unexpected state transitions during e2e test run
Description: I set the start date of the sample to be two months ago so you could see how frequent this problem is happening.
 
  
 ----
 Component Readiness has found a potential regression in the following test:
 {code:java}
 [bz-Management Console] clusteroperator/console should not change condition/Available{code}
 Probability of significant regression: 99.84%
 
 Sample (being evaluated) Release: 4.17
 Start Time: 2024-07-03T00:00:00Z
 End Time: 2024-09-04T23:59:59Z
 Success Rate: 89.24%
 Successes: 141
 Failures: 17
 Flakes: 0
 
 Base (historical) Release: 4.16
 Start Time: 2024-05-31T00:00:00Z
 End Time: 2024-06-27T23:59:59Z
 Success Rate: 100.00%
 Successes: 68
 Failures: 0
 Flakes: 1
 
 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=unknown&Suite=unknown&Topology=ha&Topology=ha&Upgrade=none&Upgrade=none&baseEndTime=2024-06-27%2023%3A59%3A59&baseRelease=4.16&baseStartTime=2024-05-31%2000%3A00%3A00&capability=Operator&columnGroupBy=Platform%2CArchitecture%2CNetwork&component=Management%20Console&confidence=95&dbGroupBy=Platform%2CArchitecture%2CNetwork%2CTopology%2CFeatureSet%2CUpgrade%2CSuite%2CInstaller&environment=amd64%20default%20upi%20ovn%20vsphere%20unknown%20ha%20none&ignoreDisruption=1&ignoreMissing=0&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-04%2023%3A59%3A59&samplePRNumber=&samplePROrg=&samplePRRepo=&sampleRelease=4.17&sampleStartTime=2024-07-03%2000%3A00%3A00&testId=openshift-tests%3Af9552d2b4b817d19bdcd666a7b8d1ece&testName=%5Bbz-Management%20Console%5D%20clusteroperator%2Fconsole%20should%20not%20change%20condition%2FAvailable]
Status: ASSIGNED
Comment 25586828 by Candace Holman at 2024-09-16T17:47:35.045+0000
The test failures for "[bz-Management Console] clusteroperator/console should not change condition/Available" started in 4.16.  This is not a 4.17 regression.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.

# [bz-Management Console] clusteroperator/console should not change condition/Available
0 unexpected clusteroperator state transitions during e2e test run, as desired.