-
Bug
-
Resolution: Done
-
Major
-
None
-
4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The CAPI provider deployment can't be reconciled on pre-existing clusters after upgrading to HyperShift Operator v0.1.63
Version-Release number of selected component (if applicable):
v0.1.63
How reproducible:
100%
Steps to Reproduce:
1. On a management cluster with existing hosted clusters, upgrade HO to v0.1.63
2.Check on ReconciliationSucceeded status for the hosted cluster
Actual results:
- lastTransitionTime: "2025-06-27T03:47:46Z"
message: 'failed to reconcile capi provider: failed to reconcile capi provider
component: Deployment.apps "capi-provider" is invalid: spec.template.metadata.labels:
Invalid value: map[string]string{"app":"capi-provider-controller-manager", "control-plane":"capi-provider-controller-manager",
"hypershift.openshift.io/control-plane-component":"capi-provider", "hypershift.openshift.io/hosted-control-plane":"agarcial-agarcial-management",
"hypershift.openshift.io/need-management-kas-access":"true"}: `selector` does
not match template `labels`'
observedGeneration: 4
reason: ReconciliationError
status: "False"
type: ReconciliationSucceeded
Expected results:
ReconciliationSucceeded should be True
Additional info:
the old selector has hypershift.openshift.io/control-plane-component: capi-provider-controller-managerbut the new deployment has hypershift.openshift.io/control-plane-component: capi-provider as the label (which matches the deployment name)