| #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 | 32 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 | |||
| pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-serial (all) - 10 runs, 100% failed, 60% of failures match = 60% impact | |||
| #1790748242145710080 | junit | 3 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| #1788902615770206208 | junit | 8 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| #1789909117905670144 | junit | 5 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| #1788631033889951744 | junit | 8 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| #1788526829313724416 | junit | 9 days ago | |
# [bz-Storage] clusteroperator/storage should not change condition/Available 0 unexpected clusteroperator state transitions during e2e test run, as desired. | |||
| #1788216689624616960 | 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 60.00% of runs (60.00% of failures) across 10 total runs and 1 jobs (100.00% failed) in 1.258s - clear search | chart view - source code located on github