We’re using MAAS 3.5 with UCS, and during the first boot after provisioning, the BMC scripts fail. As a result, attempting to “check power” raises the following error:
Failed to query node's BMC - (admin) - Aborting COMMISSIONING and reverting to NEW. Unable to power control the node. Please check power credentials.
Failed to query node's BMC - (admin) - No rack controllers can access the BMC of node server1.
The IPMI/Redfish interface is active in the profile, and there is a user created with a password.
This issue did not occur with MAAS 3.4, where the same setup worked fine. Does anyone have any suggestions or insights?
In my understanding, when we use the UCS power driver, the entire power-on/power-off process of the machine should be handled by the UCS. Is this understanding correct?
Is there any specific configuration we need to set up in the UCS? Some time ago, I managed to get everything working with version 3.4, but now, it no longer works.
@r00ta I performed a fresh installation of MAAS 3.4, and it is working correctly. There are no BMC errors when checking power, and I am able to successfully “commission” a server.
The maas_url is configured to use the HAProxy address, not the regiond address directly.
Additional Test:
I performed another test that worked successfully: I installed MAAS on a single machine using a simple command: apt install maas
Based on the documentation, the HA setup for MAAS appears to be relatively simple. It only requires configuring HAProxy and adding machines to it, as MAAS can handle the rest automatically.
The UCSM has a certificate chain, but I only added (at ca-certificates) the UCSM certificate, leaving out the CA certificates.
When I executed a curl command to the UCS URL, no errors were displayed, which gave me a false sense that everything was fine.
To make things more challenging, the error message returned by MAAS is not very helpful, as it’s just a generic error message.
It would be very helpful if an “insecure TLS” option were added to the provider. In most cases (I believe), this kind of setup is internal and often uses self-signed certificates.
How did I discover this? During the installation of MAAS 3.4, the BMC error was also displayed, but the message was much clearer. It was only after some time that I decided to try manually adding the CA’s public key.
).