-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
I'm seeing the "ClusterOperators did not settle" error in 4.14 rollback job https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.14-e2e-aws-ovn-upgrade-rollback-oldest-supported/1712420392238321664 and 4.15 rollback job https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-ovn-upgrade-rollback-oldest-supported/1712459227462635520.
Both complain:
Oct 12 14:25:58.775: INFO: Unexpected error: during upgrade to registry.build01.ci.openshift.org/ci-op-g7xbc1qf/release@sha256:861fcbad3f7abe0803dbdb077331da457edbb51b44f23637e6375ce344b24ad7:
<*errors.errorString | 0xc00203c8c0>:
ClusterOperators did not settle:
clusteroperator/kube-apiserver is Progressing for 12m16.617953895s because "NodeInstallerProgressing: 1 nodes are at revision 6; 2 nodes are at revision 7"
{
s: "ClusterOperators did not settle: \nclusteroperator/kube-apiserver is Progressing for 12m16.617953895s because \"NodeInstallerProgressing: 1 nodes are at revision 6; 2 nodes are at revision 7\"",
}
Related slack thread: https://redhat-internal.slack.com/archives/CEGKQ43CP/p1697205271643159
Please close it if it's not worth enhancement.
- is related to
-
OTA-455 Support assisted z-stream rollbacks from 4.16+
-
- Closed
-