Cluster deployed goes in failed status because a neutron API issue

[xinity]

/kind bug

What steps did you take and what happened:
I've deployed multiple cluster using CAPO without any issue, suddenly one day those clusters are in a failed state on the seed one:

looking at the logs i found a detailed status:

What did you expect to happen:
I expect all cluster to be in a provisioned state

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

i don't know how to bring back the existing deployed cluster into the provisioned state

Environment:

• Cluster API Provider OpenStack version (Or git rev-parse HEAD if manually built): 0.10.4
• Cluster-API version: 1.7.4
• OpenStack version: train
• Minikube/KIND version: 0.22.0
• Kubernetes version (use kubectl version): 1.29.2
• OS (e.g. from /etc/os-release): flatcar linux

[mnaser]

I've noticed the same but I've also noticed that the cluster continues to reconcile with no problems as well..

[xinity]

do you have any idea what could have cause the issue @mnaser ?

[mnaser]

I haven't found a way to be able to flip it back

[EmilienM]

Could you please share the CAPO object status (OpenStackCluster), thanks

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[EmilienM]

/remove-lifecycle rotten