kernel-packages team mailing list archive

[Jeff Marcom <jeff.marcom@xxxxxxxxxxxxx>]

Confirmed that the ipmi-locate command fails during the MAAS enlistment
process on OCV3 bmc.

ipmi-locate failure:
Probing KCS device using DMIDECODE... done
IPMI Version: 2.0
IPMI locate driver: DMIDECODE
IPMI interface: KCS
BMC driver device: 
BMC memory base address: 0x0
Register spacing: 1

Probing SMIC device using DMIDECODE... FAILED

Probing BT device using DMIDECODE... FAILED

Probing SSIF device using DMIDECODE... FAILED

Probing KCS device using SMBIOS... done
IPMI Version: 2.0
IPMI locate driver: SMBIOS
IPMI interface: KCS
BMC driver device: 
BMC memory base address: 0x0
Register spacing: 1

Probing SMIC device using SMBIOS... FAILED

Probing BT device using SMBIOS... FAILED

Probing SSIF device using SMBIOS... FAILED

Probing KCS device using ACPI... FAILED

Probing SMIC device using ACPI... FAILED

Probing BT device using ACPI... FAILED

Probing SSIF device using ACPI... FAILED

Probing KCS device using PCI... FAILED

Probing SMIC device using PCI... FAILED

Probing BT device using PCI... FAILED

Probing SSIF device using PCI... FAILED

-- 
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:
  New
Status in Open Compute Project:
  New
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