This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1210393
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
Status in MAAS:
Triaged
Status in Open Compute Project:
New
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
The OCPv3 Roadrunner machine has been fully enabled and passes
certification testing. When testing ipmitool locally I'm able to
setup the BMC and users, etc.
When using MAAS, MAAS is able to setup the BMC network information (I
see that it changes that), but it appears to fail to set a username
and password. If I try to use the username and password as defined in
the MAAS GUI, it fails. Therefore commissioning and juju
bootstrapping the node has to be done manually (by physically pushing
the power button).
If I use the username/password I've set on the BMC I can see that MAAS
fails to set the username 'maas' and the password as defined in the
MAAS gui.
Since the commissioning/enlisting process is temporary and I'm not
sure how to login to this phase to gather data, troubleshooting tips
are welcome.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
