-
Bug
-
Resolution: Done
-
Critical
-
ACM 2.12.0, ACM 2.12.1, ACM 2.12.2
-
Quality & Stability
-
2
-
False
-
None
-
False
-
-
-
Observability Sprint 40
-
Critical
-
None
Description of problem:
Due to a change in upstream Kubernetes, included in OCP 4.18, re-applying the observability CRD in MCH fails. This appears to happen for example on ACM upgrades, and causes the ACM upgrade to become stuck. This issue happens regardless of whether Observability is enabled in the ACM cluster.
It can also happen when making config changes, such as changing the value of disableHubSelfManagement on the MCH CR on an already running stack.
This results in an error such as below:
2025-03-20T11:23:41.528Z ERROR Reconciler error {"controller": "multiclusterhub", "controllerGroup": "operator.open-cluster-management.io", "controllerKind": "MultiClusterHub", "MultiClusterHub": {"name":"multiclusterhub","namespace":"ocm"}, "namespace": "ocm", "name": "multiclusterhub", "reconcileID": "9d1e2d6d-a6f0-4447-972c-9381b711401e", "error": "CustomResourceDefinition.apiextensions.k8s.io \"multiclusterobservabilities.observability.open-cluster-management.io\" is invalid: spec.conversion.webhookClientConfig.caBundle: Invalid value: []byte{0x5c, 0x6e}: unable to load root certificates: unable to parse bytes as PEM block"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.5/pkg/internal/controller/controller.go:324
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.5/pkg/internal/controller/controller.go:261
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.5/pkg/internal/controller/controller.go:222
Version-Release number of selected component (if applicable):
Any ACM version on OCP 4.18
How reproducible:
Always
Steps to Reproduce:
Method 1)
- Install any ACM version on OCP 4.18 (but don't install the latest)
- Upgrade ACM to a later version (i.e install 2.12, upgrade to 2.13, or install 2.12.0 and upgrade to 2.12.2)
Method 2)
- Install ACM and create an MCH (make sure the install finish)
- Set disableHubSelfManagement from true to false
Actual results:
MCH gets stuck, showing the error. It can be seen by
oc get multiclusterhubs -n open-cluster-management -o yaml
Expected results:
MCH should succeed in re-applying the MCO CRD and any changes (upgrades, or disabling hub self management) should work.
Additional info:
NA
- clones
-
-
- Closed
-