Bug 2072348
Summary: | Upgrade Precondition "EtcdRecentBackup" failed because of "ControllerStarted" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ge liu <geliu> |
Component: | Installer | Assignee: | aos-install |
Installer sub component: | openshift-installer | QA Contact: | Gaoyun Pei <gpei> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | high | ||
Priority: | unspecified | CC: | wking |
Version: | 4.10 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-06 06:17:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 1
W. Trevor King
2022-04-06 05:56:25 UTC
From comment 3's must-gather: $ yaml2json <cluster-scoped-resources/config.openshift.io/clusterversions/version.yaml | jq -r '.status.conditions[] | .lastTransitionTime + " " + .type + "=" + .status + " " + .reason + ": " + .message' 2022-04-06T05:06:36Z Available=True : Done applying 4.9.26 2022-04-06T05:55:30Z Failing=False : 2022-04-06T05:27:06Z Progressing=True ClusterOperatorUpdating: Working towards 4.10.6: 205 of 771 done (26% complete), waiting on machine-api 2022-04-06T05:26:09Z RetrievedUpdates=True : 2022-04-06T05:35:07Z Upgradeable=False KubeletMinorVersion_KubeletMinorVersionUnsupportedNextUpgrade: Cluster operator kube-apiserver should not be upgraded between minor versions: KubeletMinorVersionUpgradeable: Kubelet minor versions on 5 nodes will not be supported in the next OpenShift minor version upgrade. So looks like the CVO was briefly waiting on etcd to do the pre-minor-update backup dance, and now everything is going smoothly? [1] walks through the dance and points out some higher-latency steps, and [2] seems to be directly scoping that bug to Upgradeable-check latency, so I'll close this one as a dup of [2]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2061444#c4 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=2006611#c7 *** This bug has been marked as a duplicate of bug 2006611 *** Yes, this bug is duplicate with 2061444 |