-
Bug
-
Resolution: Done
-
Blocker
-
None
-
4.21
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
4.21.0-0.nightly-2025-12-10-193741 and 4.21.0-0.ci-2025-12-10-174129 are failing micro upgrades with
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:189]: during upgrade to registry.build09.ci.openshift.org/ci-op-fcdfjnkq/release@sha256:139eeb0b08dfbcb85e1008c548052ddbd8da3faf4b87b91fbb79c10f07662609: Cluster did not complete upgrade: timed out waiting for the condition: Could not update customresourcedefinition "ipaddressclaims.ipam.cluster.x-k8s.io" (187 of 967): the object is invalid, possibly due to local cluster configuration}
Those payloads contain Pin IPAM CRDs to release-4.20 - Started a revert
Impacts Tests:
verify the cluster readiness and stability [Monitor:legacy-cvo-invariants][bz-kube-apiserver] clusteroperator/kube-apiserver should stay Progressing=False while MCO is Progressing=True [Monitor:legacy-cvo-invariants][bz-kube-controller-manager] clusteroperator/kube-controller-manager should stay Progressing=False while MCO is Progressing=True [Monitor:legacy-cvo-invariants][bz-kube-scheduler] clusteroperator/kube-scheduler should stay Progressing=False while MCO is Progressing=True [Monitor:legacy-cvo-invariants][bz-Cloud Compute] clusteroperator/machine-api should stay Progressing=False while MCO is Progressing=True [Monitor:legacy-test-framework-invariants-alerts][bz-Cluster Version Operator][invariant] alert/ClusterOperatorDegraded should not be at or above info [sig-arch][Feature:ClusterUpgrade] Cluster should be upgradeable after finishing upgrade [Late][Suite:upgrade] [sig-cluster-lifecycle] Cluster completes upgrade