-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
co/authentication reported Progressing=True when a cluster is scaling up which should not happened during a normal cluster upgrade.
Job example 1 and Job example 2
: [sig-cluster-lifecycle][Feature:Machines][Serial] Managed cluster should grow and decrease when scaling different machineSets simultaneously [Timeout:30m][apigroup:machine.openshift.io] [Suite:openshift/conformance/serial] expand_less 8m7s
{ fail [github.com/openshift/origin/test/extended/machines/scale.go:267]: those cluster operators left Progressing=False while cluster was scaling: [authentication]
Expected
<[]string | len:1, cap:1>: ["authentication"]
to be empty}
How reproducible:
Occasionally on aws-ovn-single-node clusters.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
co does not go Progressing=True when a cluster is scaling up
Additional info:
- relates to
-
OTA-1637 Fail CI if any Cluster Operator reports Progressing=True only up to cluster scaling or a node rebooting
-
- Closed
-