CAPO request to create a already existing VM

[hugoprudente]

/kind bug

What steps did you take and what happened:

Cluster was running happy there was not reboot on the June 28 VM but somehow I got a trigger and it created another VM.

dub-md-2-78fkp centos-9-kube-v1.28.8-g8912.2 Sept. 10, 2024, 10:25 p.m.
dub-md-2-78fkp centos-9-kube-v1.28.8-g8912.2 June 28, 2024, 11:22 a.m.

What did you expect to happen:

No duplicate VMs if the VM is not deleted from Openstack side.

Anything else you would like to add:

Environment:

• Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): v0.9.0
• Cluster-API version: v1.6.3
• OpenStack version: Yoga
• Minikube/KIND version:
• Kubernetes version (use kubectl version):1.28.8
• OS (e.g. from /etc/os-release): centos-9 stream

[EmilienM]

please provide CAPO logs (sanitized with no company data) so we can see what trigrered that.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[EmilienM]

I think this was solved in v0.11 with OpenStackServer therefore we wouldn't spend much time fixing that in 0.9 unless it's an issue one would hit frequently.

[hugoprudente]

Thanks! It didn't happened again since I opened the issue so I could get fresh logs.

I"m on the path to update to 0.11 thanks.