Hi Douglas,

If MAAS cannot set the boot order to PXE, it doesn't matter, because
that's a best-effort and not something that causes a failure.

The failure, however, is that your BMC is either reporting that it is
failing ti power on, failing to report it was powered on correctly, or
not reporting it at all. MAAS does this:

1. MAAS attempts to set the machine to PXE boot. If it fails, it doens't 
matter, it continues.
2. MAAS tells the machine to power on and checks if it powered on. If it didn't 
power on, it re-attempts to power on and check if it powered on.

MAAS does 2 in an interval of (1, 2, 2, 4, 6, 8, 12) seconds, unless the
tool reports there's fatal errors.

That said, the times we have typically seen the issues you are
reporting, although very few cases, it have been due to a buggy BMC that
locks itself up. As such, I would recommend you try by upgrading the

Once that, could you also provide the output of:

ipmipower -W opensesspriv -D LAN_2_0 -u <user> -p <password> -h <host> --cycle 
ipmipower -W opensesspriv -D LAN_2_0 -u <user> -p <password> -h <host> --stat

And repeat that, if you can script it to see if your BMC locks or
reports an failure?

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  ipmi-config connection timeout

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to