opencompute-developers team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

This bug was nominated against a series that is no longer supported, ie
saucy.  The bug task representing the saucy nomination is being closed
as Won't Fix.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu Saucy)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Open
Compute Developers, which is subscribed to The Open Compute Project.
Matching subscriptions: Open Compute BUGs
https://bugs.launchpad.net/bugs/1210393

Title:
  MAAS ipmi fails on OCPv3 Roadrunner

Status in MAAS:
  Fix Released
Status in Open Compute Project:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Won't Fix

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