-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.21.0
-
None
-
None
-
False
-
-
3
-
Important
-
None
-
None
-
None
-
Rejected
-
Umbreon Sprint 281
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
A component must not report Available=False during the course of a normal upgrade:
https://github.com/openshift/api/blob/master/config/v1/types_cluster_operator.go#L156
: [Monitor:legacy-cvo-invariants][bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should not change condition/Available expand_lessRun #0: Failed expand_less1h35m42s{ 0 unexpected clusteroperator state transitions during e2e test run, as desired.
3 unwelcome but acceptable clusteroperator state transitions during e2e test run. These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
Dec 09 08:30:59.321 E clusteroperator/operator-lifecycle-manager-packageserver condition/Available reason/ClusterServiceVersionNotSucceeded status/False ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: ComponentUnhealthy, message: apiServices not installed (exception: Operator operator-lifecycle-manager-packageserver is in Available=False state running in single replica control plane, expected availability transition during upgrade)
Dec 09 08:30:59.321 - 16s E clusteroperator/operator-lifecycle-manager-packageserver condition/Available reason/ClusterServiceVersionNotSucceeded status/False ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: ComponentUnhealthy, message: apiServices not installed (exception: Operator operator-lifecycle-manager-packageserver is in Available=False state running in single replica control plane, expected availability transition during upgrade)
Dec 09 08:31:15.617 W clusteroperator/operator-lifecycle-manager-packageserver condition/Available reason/ClusterServiceVersionSucceeded status/True ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Succeeded (exception: Available=True is the happy case)
}
Version-Release number of selected component (if applicable):
How reproducible:
Run https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node/1998279230936322048 , check the Flaky section.
Steps to Reproduce:
1.
2.
3.
Actual results:
clusteroperator/operator-lifecycle-manager-packageserver condition/Available reason/ClusterServiceVersionNotSucceeded status/False ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: ComponentUnhealthy, message: apiServices not installed
Expected results:
A component must not report Available=False during the course of a normal upgrade.
Additional info:
- is related to
-
-
- Verified
-
- relates to
-
OTA-1637 Fail CI if any Cluster Operator reports Progressing=True only up to cluster scaling or a node rebooting
-
- Closed
-
- links to