[Expired for maas (Ubuntu) because there has been no activity for 60
days.]
** Changed in: maas (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762555
Apologies, I thought I responded to this a while ago. After switching
the cable to the dedicated IPMI nic, everything seemed to work out
without an issue. Kind of sucks that the shared IPMI flakes out but it
is what it is. Thanks for your help!
--
You received this bug notification because you
Andres,
Thanks for the quick reply and the info on the MaaS subsystem. A couple things
I have noticed:
1. MaaS can power on/off the machine correctly and can detect that the system
is either power on/off.
2. I believe the servers I'm trying to boot are using shared nics which seem to
flap when
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
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762555
Title:
ipmi-config connection timeout
To manage notifications about this bug go
