← Back to team overview

kernel-packages team mailing list archive

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


Troubleshooting steps:

modprobe ipmi_msghandler
modprobe ipmi_devintf
modprobe ipmi_si

Will enable the bmc device parameters to be changed locally and
eliminate the write back errors, something I feel the Saucy ephemeral
images are not doing.

Secondly, trying to enable link authentication fails to set:
 ipmitool lan set 1 auth ADMIN MD5,PASSWORD

Channel link access still states:
User ID : 4

User Name : admin

Fixed Name : No

Access Available : call-in / callback

Link Authentication : disabled

IPMI Messaging : enabled

Also, setting link access for channel 1 fails:

sudo ipmitool lan set 1 access on
Set Channel Access for channel 1 failed: Unknown (0x83)

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:

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: