Cluster Install Failed: SettingProviderIDOnNodeFailed

[abmoussaoui]

Hello Community

What steps did you take and what happened:
After initiating the cluster deployment process, everything seems to be progressing normally until it reaches a point where it gets stuck with the status "SettingProviderIDOnNodeFailed" in the Cluster CRD.

Questions:

• What could be causing the "SettingProviderIDOnNodeFailed" status in the Cluster CRD during the deployment process?
• Are there any specific logs or debugging steps that I should be looking at to diagnose this issue further?
• Are there any known issues or common pitfalls related to the interaction between ClusterAPI, CAPM3, and the Metal3 provider that could lead to this error?

Cluster Status msg:
Status:
Conditions:
Last Transition Time: 2024-02-28T09:59:40Z
Message: 1 of 2 completed
Reason: SettingProviderIDOnNodeFailed @ /hp-mbmff
Severity: Error
Status: False
Type: Ready

What did you expect to happen:
Kubernetes on a newly created BMH controlled using IPMI
OS image: UBUNTU_22.04_NODE_IMAGE_K8S_v1.29.0-raw.qcow2

Environment:

• Cluster-api version: 1.6.0
• Cluster-api-provider-metal3 version: 1.6.0
• Environment (metal3-dev-env or other): BMO? Ironic , CAPI
• Kubernetes version: (use kubectl version): v1.28.7

/kind bug

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[Rozzii]

Hi we have seen similar issue in the past but we would need some logs and other metadata , could you please share:

• the BMO logs,
• Ironic container logs
• BMH CR of the related node
• M3M cr of the related node
• If possible MachineDeployment CR
• If you have access to the serial logs when the machine boots that would be nice also

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale