-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
None
-
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 console operator that blips Degraded=True Example Job 1: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade/1865645547616997376 Example Job 2: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-upgrade-from-stable-4.18-e2e-aws-ovn-upgrade/1865373749625229312 Reasons associated with the blip could be PDBSync_FailedApply, DeploymentSync_FailedApply, ConsoleCustomRouteSync_FailedDeleteCustomRoutes, ConfigMapSync_FailedApply 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. See linked issue for more explanation on the effort. Exception code is here: https://github.com/openshift/origin/blob/34565b0cc783d389fa559a993dca62e0dd4e0d8a/pkg/monitortests/clusterversionoperator/legacycvomonitortests/operators.go#L306
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