-
Bug
-
Resolution: Not a Bug
-
Critical
-
ACM 2.15.1
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Installer Train 35 - 2, Installer Train 36 - 3
-
Important
-
None
Description of problem:
When using the stable-2.9 channel with the latest MCE 2.10.1 image, MCE fails to install due to this error in the MCE operator pod.
2026-01-15T12:42:10.451Z INFO setup Disabling Operator Client Cache for high-memory resources 2026-01-15T12:42:10.554Z INFO setup Setting OperatorCondition. 2026-01-15T12:42:13.258Z INFO setup Updating CRD {"Name": "agentclassifications.agent-install.openshift.io"} 2026-01-15T12:42:13.274Z INFO setup Updating CRD {"Name": "agents.agent-install.openshift.io"} 2026-01-15T12:42:13.449Z INFO setup Updating CRD {"Name": "agentserviceconfigs.agent-install.openshift.io"} 2026-01-15T12:42:13.576Z INFO setup Updating CRD {"Name": "hypershiftagentserviceconfigs.agent-install.openshift.io"} 2026-01-15T12:42:13.600Z INFO setup Updating CRD {"Name": "infraenvs.agent-install.openshift.io"} 2026-01-15T12:42:13.619Z INFO setup Updating CRD {"Name": "nmstateconfigs.agent-install.openshift.io"} 2026-01-15T12:42:13.629Z INFO setup Updating CRD {"Name": "agentclusterinstalls.extensions.hive.openshift.io"} 2026-01-15T12:42:13.671Z INFO setup Updating CRD {"Name": "clusterclasses.cluster.x-k8s.io"} 2026-01-15T12:42:13.730Z ERROR setup unable to ensure CRD exists in alloted time. Failing. main.main /workspace/main.go:309 runtime.main /usr/lib/golang/src/runtime/proc.go:283
Note that this also happens if you try to install 2.14 directly from these images:
"acm_image": "quay.io:443/acm-d/acm-dev-catalog:2.14.2-DOWNSTREAM-2026-01-14-19-16-48",
"mce_image": "quay.io:443/acm-d/mce-dev-catalog:2.9.2-DOWNSTREAM-2026-01-14-19-20-53",
Upon analysis, this is because some CAPI CRDs had their spec.versions updated in higher version of MCE, so if one of those is installed first, it will prevent MCE 2.9 from installing. Uninstallation will not delete this CRDs and as a workaround, you can manually delete them.
oc delete crd clusterclasses.cluster.x-k8s.io oc delete crd clusterresourcesetbindings.addons.cluster.x-k8s.io oc delete crd clusterresourcesets.addons.cluster.x-k8s.io oc delete crd clusters.cluster.x-k8s.io oc delete crd extensionconfigs.runtime.cluster.x-k8s.io oc delete crd machinedeployments.cluster.x-k8s.io oc delete crd machinedrainrules.cluster.x-k8s.io oc delete crd machinehealthchecks.cluster.x-k8s.io oc delete crd machinepools.cluster.x-k8s.io oc delete crd machines.cluster.x-k8s.io oc delete crd machinesets.cluster.x-k8s.io
Version-Release number of selected component (if applicable):
"acm_image": "quay.io:443/acm-d/acm-dev-catalog:2.15.1-DOWNSTREAM-2026-01-15-00-22-12",
"mce_image": "quay.io:443/acm-d/mce-dev-catalog:2.10.1-DOWNSTREAM-2026-01-15-06-17-41",
How reproducible:
Always
Steps to Reproduce:
- Install MCE 2.11
- Uninstall MCE 2.11
- Install MCE 2.9
Actual results:
Error described above
Expected results:
Should work
-------------------------------------------------------------------------------------------------------
QE Hand Off Template (fill out when moving to Review) 1/22/26:
Summary of the Work:
What was implemented or fixed? Include a brief description of the problem (if applicable) and how it was addressed.
e.g., "Updated the UI to show validation errors for the form. The previous implementation did not surface backend validation issues."
- No changes were implemented for this defect. Please refer to the comment below.
Key Areas to Verify:
- What functionality should QE focus on? List what was tested or what is most important to validate.
- Ensure the new validation messages appear for required fields
- Confirm the workflow still completes as expected after validation fixes
- Any edge cases or high-risk areas touched by the change
Fix or Feature Availability:
When will this be available in a build?
Code merged on: YYYY-MM-DD
Expected downstream build tag (if known): example-build-tag
(Optional) Related PR(s): Link
