-
Bug
-
Resolution: Done
-
Normal
-
None
-
Quality / Stability / Reliability
-
2
-
False
-
-
False
-
-
-
Installer Sprint 2025-60, Installer Sprint 2025-61
-
Low
-
None
Description of problem:
There is a false positive of running even if a crd fails to apply
Version-Release number of selected component (if applicable):
Upgrading to ACM 2.12 or ACM 2.13 on ocp 4.18
How reproducible: always
Steps to Reproduce:
- Upgrade to either ACM 2.13 and ACM 2.12
- Attempt to disable local-cluster
Actual results:
conditions:
- lastTransitionTime: '2025-03-20T17:52:37Z'
lastUpdateTime: '2025-03-20T17:52:37Z'
message: All hub components ready.
reason: ComponentsAvailable
status: 'True'
type: Complete
- lastTransitionTime: '2025-03-20T18:01:51Z'
lastUpdateTime: '2025-03-20T18:01:51Z'
message: 'Error installing CRDs: 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'
reason: FailedDeployingComponent
status: 'False'
type: Progressing
currentVersion: 2.13.0
desiredVersion: 2.13.0
phase: Running
Expected results: expect status.phase to not be running
Additional info: https://issues.redhat.com/browse/ACM-19094 related issue
- is related to
-
ACM-19094 MCH cannot re-apply MCO CRD on OCP4.18 (ACM upgrades on OCP4.18 fail)
-
- Closed
-