@Igor, we have exactly the same behaviour on HP ProLiant DL380 Gen11
I know we can change the boot order (next boot order) while the machine is off. The only restrictions is during POST and this is exactly why the power management failed via redfish from time to time (quite often in fact)
@Igor, we have exactly the same behaviour on HP ProLiant DL380 Gen11
I know we can change the boot order (next boot order) while the machine is off. The only restrictions is during POST and this is exactly why the power management failed via redfish from time to time (quite often in fact)
The problem is that power_query is unable to send back details if we are in POST or not. I guess the implementation should do a retry on the PXE boot order https:/ /github. com/canonical/ maas/blob/ de2288e04a9ad6f ee7dd8954f6502d 754f2ef280/ src/provisionin gserver/ drivers/ power/redfish. py#L272
Maybe in the spirit of what is done for ipmi (which we don't want to use as it is not enabled over LAN by default in ILO) : https:/ /github. com/canonical/ maas/blob/ de2288e04a9ad6f ee7dd8954f6502d 754f2ef280/ src/provisionin gserver/ drivers/ power/ipmi. py#L488
We are using maas 3.4.2