← Back to team overview

kernel-packages team mailing list archive

[Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner


So basically I was able to get this to work in maas.

Basically you need to change the following line in :

    def commit_ipmi_user_settings(user, password):
    ipmi_user_number = get_ipmi_user_number(user)
    if ipmi_user_number is None:
        (status, output) = commands.getstatusoutput('bmc-config --commit --key-pair="User10:Username=%s"' % user)
        ipmi_user_number = get_ipmi_user_number(user)

You have to change User10 to User4, as this bmc config maxes out at 4
User sections.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  MAAS ipmi fails on OCPv3 Roadrunner

Status in MAAS:
Status in Open Compute Project:
Status in “linux” package in Ubuntu:
Status in “linux” source package in Saucy:

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: