| #TRT-1599 | issue | 8 days ago | Setup new vsphere informing job CLOSED |
{code:java}
: [bz-Storage] clusteroperator/storage should not change condition/Available
{
| |||
| #OCPBUGS-29126 | issue | 30 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 | |||
| periodic-ci-openshift-release-master-ci-4.15-e2e-aws-upgrade-ovn-single-node (all) - 2 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1790718752870895616 | junit | 3 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run. These did not match any known exceptions, so they cause this test-case to fail: | |||
| #1788181918433415168 | junit | 10 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run. These did not match any known exceptions, so they cause this test-case to fail: | |||
Found in 100.00% of runs (100.00% of failures) across 2 total runs and 1 jobs (100.00% failed) in 90ms - clear search | chart view - source code located on github