#OCPBUGS-29126 | issue | 25 hours ago | Storage operators could flap during upgrade Verified |
Comment 24722659 by Wei Duan at 2024-05-14T07:01:27.196+0000 The case [bz-Storage] clusteroperator/storage should not change condition/Available passed in latest CI job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-vsphere-ovn-upgrade/1790112534854897664 | |||
#TRT-1599 | issue | 7 days ago | Setup new vsphere informing job CLOSED |
{code:java} : [bz-Storage] clusteroperator/storage should not change condition/Available { | |||
pull-ci-rh-ecosystem-edge-recert-main-e2e-aws-ovn-single-node-recert-serial (all) - 12 runs, 42% failed, 100% of failures match = 42% impact | |||
#1790405743938113536 | junit | 3 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
#1788917218638041088 | junit | 7 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
#1788705027401977856 | junit | 8 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
#1788591193135779840 | junit | 8 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
#1787766563768635392 | junit | 10 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. |
Found in 41.67% of runs (100.00% of failures) across 12 total runs and 1 jobs (41.67% failed) in 83ms - clear search | chart view - source code located on github