MAAS not auto-detecting/auto-entering credentials for HP Proliant ML310E G8 V2 server

[Rod Smith]

When enlisting an HP Proliant ML310E G8 V2 server, MAAS (1.7.5+bzr3369-0ubuntu1~trusty1) failed to detect the power type. (It uses IPMI 2.0.) Entering the information manually enabled MAAS to control the server. Some information from the iLO:

System ROM P78 09/01/2013
iLO Firmware Version 1.32 Nov 05 2013
Server Platform Services (SPS) Firmware 3.0.4.D1.B
HP ProLiant System ROM 09/01/2013

The iLO self-test shows the following:

Embedded Flash/SD-CARD Controller firmware revision 2.09.00 Could not partition embedded media device

MAAS server information:

$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================================-===========================================-============-===============================================================================
ii maas 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cert-server 0.2.5-0~31~ubuntu14.04.1 all Ubuntu certification support files for MAAS server
ii maas-cli 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.7.5+bzr3369-0ubuntu1~trusty1 all MAAS server provisioning libraries

I'm attaching the MAAS server's /var/log/maas/ directory tree as a tarball. Sorry it's so big; we've been doing a lot of testing lately.

[Andres Rodriguez (andreserl)]

Hi Rod,

I don't think it matters, but ubuntu trusty -updates currently has 1.7.6 and the version of MAAS being used here is 1.7.5. That being said, that seems like an enablement bug. In order to successfully debug this, we would need the console log of the machine booting and running through the commissioning environment.

Can you please provide that? Furthermore, as this is a bug that actually requires enablement, I'll assign this to newell.

[Rod Smith (rodsmith)]

Additional information: I deleted the pre-existing "maas" user on the server and tried again. This time the enlistment succeeded. I've been unable to get the bug to recur, even by resetting the "maas" user's password to its original value ("maas12345"). Thus, I suspect there was something wonky about that user's configuration in the BMC. There may well be something that MAAS can do to handle such situations better, but this bug will probably have to be tabled unless/until it can be reliably reproduced.

[Andres Rodriguez (andreserl)]

For the time being then, I'll be marking this bug as incomplete provided it cannot be reproduced.

[Launchpad Janitor (janitor)]

[Expired for maas (Ubuntu) because there has been no activity for 60 days.]

[Jeff Lane  (bladernr)]

Removing the blocker tag since this is no longer reproducible.

[Gavin Panella (allenap)]

I'm assuming this is no longer a bug.

[Rod Smith (rodsmith)]

The bug may or may not still exist, but I've been unable to reproduce it since deleting and re-creating the "maas" user on the affected system, as noted in comment #3, above.