-
Notifications
You must be signed in to change notification settings - Fork 87
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
Metal3DataTemplate with templateReference cannot be deleted while Metal3Data with matching name exists #1357
Comments
/triage accepted |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
What steps did you take and what happened:
templateReference
.What did you expect to happen:
Old Metal3DataTemplates should be possible to delete when they are no longer used.
Anything else you would like to add:
The issue happens only when using
templateReference
. It is unclear to me what the function of this field is.I have been able to do rollouts without issues when not using the
templateReference
and can then delete the old Metal3DataTemplate.Relevant docs: https://github.com/metal3-io/cluster-api-provider-metal3/blob/main/docs/api.md#updating-metadata-and-networkdata
I do not understand why the Metal3Data must be linked to both Metal3DataTemplates. It works just fine without from my experience.
Relevant code:
cluster-api-provider-metal3/baremetal/metal3datatemplate_manager.go
Lines 150 to 164 in 7d9f21c
Environment:
kubectl version
): v1.28.3/kind bug
The text was updated successfully, but these errors were encountered: