Description of problem: OCP cannot be upgraded after CNV upgrade Version-Release number of selected component (if applicable): How reproducible: 100 Steps to Reproduce: 1.Deploy ocp-4.3.10-cnv-2.2.0 2.Upgrade cnv to 2.3.0 3.upgrade OCP to 4.4.0-rc.8 Actual results: Unable to apply 4.4.0-rc.8: the cluster operator etcd is degraded Expected results: ocp is upgraded to 4.4.0-rc.8 Additional info: I'm using virt-cdi-operator-container-v2.3.0-41 (the version with the CDI SCC fix) output of oc get events: openshift-etcd-operator 47m Normal OperatorStatusChanged deployment/etcd-operator Status for clusteroperator/etcd changed: Degraded message changed from "EtcdMembersControllerDegraded: rpc error: code = Canceled desc = grpc: the client connection is closing\nStaticPodsDegraded: nodes/host-172-16-0-28 pods/etcd-host-172-16-0-28 container=\"etcd\" is not ready\nStaticPodsDegraded: nodes/host-172-16-0-28 pods/etcd-host-172-16-0-28 container=\"etcd\" is waiting: \"CrashLoopBackOff\" - \"back-off 5m0s restarting failed container=etcd pod=etcd-host-172-16-0-28_openshift-etcd(a76f260fbdd0ccaacd016e9f86b2d367)\"\nStaticPodsDegraded: pods \"etcd-host-172-16-0-12\" not found\nStaticPodsDegraded: pods \"etcd-host-172-16-0-25\" not found" to "EtcdMembersControllerDegraded: rpc error: code = Canceled desc = grpc: the client connection is closing\nStaticPodsDegraded: nodes/host-172-16-0-28 pods/etcd-host-172-16-0-28 container=\"etcd\" is not ready\nStaticPodsDegraded: pods \"etcd-host-172-16-0-12\" not found\nStaticPodsDegraded: pods \"etcd-host-172-16-0-25\" not found" openshift-etcd 42m Normal Pulled pod/etcd-host-172-16-0-28 Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3fca9e34ee55702944f0d6ff58704289cbcda6667c150bdb48890ccc13d0dedf" already present on machine openshift-etcd 2m17s Warning BackOff pod/etcd-host-172-16-0-28 Back-off restarting failed container openshift-machine-config-operator 3m51s Warning Unhealthy pod/etcd-quorum-guard-86d65b5bd6-ltqfl Readiness probe failed:
@ginger, could u help to try it again with cnv upgrade? thanks
*** This bug has been marked as a duplicate of bug 1830510 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days