-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
None
-
False
-
Description of problem:
In an effort to ensure all HA components are not degraded by design during normal e2e test or upgrades, we are collecting all operators that are blipping Degraded=True during any payload job run. This card captures network operator that blips Degraded=True during upgrade runs. Example Job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade/1848707329046876160 Reasons associated with the blip: ApplyOperatorConfig, NoOperConfig, BootstrapError etc For now, we put an exception in the test. But it is expected that teams take action to fix those and remove the exceptions after the fix go in. Exception is defined here: https://github.com/openshift/origin/blob/9a6a83bf56952bd58929aa5d68b0986a2ccf4b8c/pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go#L391 See linked issue for more explanation on the effort.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- impacts account
-
TRT-1578 Ensure all HA components are not degraded by design during upgrades
- New
- relates to
-
OCPBUGS-38684 clusteroperator/network blips Degraded=True during serial test
- New