-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSA: ClusterClass with MHC fails #6653
Comments
/assign Note: Seems to only happen for MHC defined for ControlPlanes. MHC for a MachineDeployment via ClusterClass seems to be fine. |
When comparing MHC for MachineDeployments and ControlPlanes on ClusterClass:
I see two solutions:
I favor for 1, because this would make the behaviour consistent to what is done for MachineDeployments. |
|
Note: Let's please extend our e2e test ClusterClasses to also include CP+MD MHC's. I think it should be a trivial change and this should allow us to at least detect if the MHC reconciliation breaks anything (I wouldn't go so far to verify if the MHC actually works, just adding it) |
Has been fixed in #6660 /close |
@sbueringer: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm creating a ClusterClass with MHC and the reconciler fails with the following error
Error message:
Stacktrace (thx JSON logging!)
The problem is the following:
desired_state.go
we are copying over the owner rev of the previous MHC:cluster-api/internal/controllers/topology/cluster/desired_state.go
Lines 828 to 832 in abb8f5f
reconcile_state.go
we overwrite the ownerReferences:cluster-api/internal/controllers/topology/cluster/reconcile_state.go
Lines 255 to 257 in 2f6f77f
s.Desired.ControlPlane.Object
does not contain a UID so the ref also doesn't contain itreconcileMachineHealthCheck
we only callresolveOwnerReferenceIfIncomplete
if the MHC is initially created, on updates we don't do it and thus try to patch a MHC with an empty UID, which leads to the error above/kind bug
/area topology
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: