kernel-packages team mailing list archive

[Jeff Lane <jeffrey.lane@xxxxxxxxxxxxx>]

why not have it look for an existing user called maas, and if none is
present, have it walk the slots starting at 0 until it finds an empty or
runs out of spaces?

Or is that one of those weird things that seem simple on paper, but in
practice are really actually difficult to do because of some IPMI issue
or design?

Anyway, just curious.

-- 
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:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed

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