MAAS is trying to configure IPMI because it's failing to detect the Redfish interface:
INFO: Checking for HP Moonshot...
INFO: Checking for Redfish...
ERROR: Redfish configuration failed. Missing SMBIOS data
INFO: Checking for IPMI...
INFO: IPMI detected!
INFO: Reading current IPMI BMC values...
If we look at the output of 'dmidecode -t 42', it's in fact missing the info we expect:
Handle 0x00D0, DMI type 42, 169 bytes
Management Controller Host Interface
Host Interface Type: Network
(...)
idVendor: 0x04b3
idProduct: 0x4010
Protocol ID: 04 (Redfish over IP)
Service UUID: a4b13f22-d0f3-11ea-aca9-e5b8d327f39f
(...)
I'm not sure that we can work-around this. Commissioning scripts run in an untrusted environment, so they cannot fetch any host-specific data from MAAS to make up for the missing data, and without it the Redfish setup should fail and the script should attempt to configure IPMI (which kind of succeeded).
MAAS is trying to configure IPMI because it's failing to detect the Redfish interface:
INFO: Checking for HP Moonshot...
INFO: Checking for Redfish...
ERROR: Redfish configuration failed. Missing SMBIOS data
INFO: Checking for IPMI...
INFO: IPMI detected!
INFO: Reading current IPMI BMC values...
If we look at the output of 'dmidecode -t 42', it's in fact missing the info we expect:
Handle 0x0024, DMI type 42, 12 bytes
Management Controller Host Interface
We expect something like:
Handle 0x00D0, DMI type 42, 169 bytes d0f3-11ea- aca9-e5b8d327f3 9f
Management Controller Host Interface
Host Interface Type: Network
(...)
idVendor: 0x04b3
idProduct: 0x4010
Protocol ID: 04 (Redfish over IP)
Service UUID: a4b13f22-
(...)
I'm not sure that we can work-around this. Commissioning scripts run in an untrusted environment, so they cannot fetch any host-specific data from MAAS to make up for the missing data, and without it the Redfish setup should fail and the script should attempt to configure IPMI (which kind of succeeded).