Open fracappa opened 1 month ago
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.
@kashifest @Rozzii PTAL?
@fracappa Based on the error message and the fact that you can't see the state of the BMH I would say that it is a "Basic Authentication issue" the deploy script makes sure that BMO and Ironic uses the same credential for the Ironic API but you are deploying BMO without the script and Ironic with the script.
I would recommend deploying BOM and Ironic together like this:
./baremetal-operator/tools/deploy.sh -b -i
AFAIK this is not an Idrac specific issue simply a miss configured BAUTH
setup.
I will remove the bug label for now.
/triage needs-information
Steps I followed
Hello everyone.
I'm using the baremetal-operator to manage my on-premise cluster where I have Dell servers, equipped with iDRAC 9.
I deploy the metal3 provider like the following:
and then:
clusterctl init --infrastructure metal3
Whereas, I install the baremetal operator in the following way:
as specified in the metal3-provider github repository.
Then, I also deploy the ironic pods after customizing the env var files in this way:
./baremetal-operator/tools/deploy.sh -i
.After the setup, I try to create my BMH resources this way:
What happened
I expect that the BMH resource would go to the
registering
state, and then moving toinspecting
,provisioning
andprovisioned
.However, the resource has no STATUS and it looks like this:
More details
Moreover, when I inspect the logs of the ironic pods I have these:
Environment:
/kind bug