-
Bug
-
Resolution: Unresolved
-
Minor
-
ACM 2.14.0, ACM 2.14.1
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Low
-
None
Description of problem:
The MCO status never recovers from a failed state, if MCOA was enabled, without providing the correct CRDs (manually in 2.14)
Version-Release number of selected component (if applicable):
ACM 2.14
How reproducible:
Always
Steps to Reproduce:
- Install MCO on ACM 2.14, add at least one spoke
- Enable metrics/incident detection/log collection, for example:
spec:
capabilities:
platform:
metrics:
collection:
enabled: true
- `oc get mco observability -o yaml` shows degraded state: MultiClusterObservabilityAddonDegraded
- lastTransitionTime: "2025-11-05T05:41:47Z"
message: 'MultiCluster-Observability-Addon degraded because the following CRDs
are not installed on the hub: prometheusagents.monitoring.coreos.com(v1alpha1)'
reason: MultiClusterObservabilityAddonDegraded
status: "True"
type: MultiClusterObservabilityAddonDegraded
- Disable again:
spec:
capabilities:
platform: {}
Actual results:
Degraded state goes away
Expected results:
Degraded state never recovers