MAAS fails to detect Huawei-based server's power type

Bug #1703406 reported by Samantha Jian-Pielak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Incomplete
Undecided
Unassigned

Bug Description

Running the latest MAAS 2.2, MAAS doesn't detect Huawei-based server's power type.

subprocess.CalledProcessError: Command '('bmc-config', '--commit', '--key-pair=User3:Password=e6YO0LESFrJ5Ca7')' returned non-zero exit status 1

cloud-init-output.log: http://paste.ubuntu.com/25043798/
cloud-init.log: http://paste.ubuntu.com/25043799/

Changed in maas:
milestone: none → 2.3.0
status: New → Incomplete
Revision history for this message
Andres Rodriguez (andreserl) wrote :

This seems like the BMC didn't allow committing that password for the created used, which could be a BMC issue or a change in how IPMI is handled in this new hardware. Have you tried manually to check that:

1. The BMC has User3
2. You can manually commit the password yourself?

Also, I believe that this could be a duplicate of https://bugs.launchpad.net/maas/+bug/1621175. If that';s the case, the password policy of this BMC doesn't seem to be compliant with the IPMI spec, which doesn't seem to have minimum password requirements.

Revision history for this message
Samantha Jian-Pielak (samantha-jian) wrote :

It's a duplicate of bug 1621175.

This time it failed with this key pair commit:
--key-pair=User3:Password=mEke5lpiBDTcm

User 3 exists:
ubuntu@actual-osprey:~$ sudo ipmitool user list 1
ID Name Callin Link Auth IPMI Msg Channel Priv Limit
1 true true true NO ACCESS
2 Administrator true true true ADMINISTRATOR
3 maas true true true NO ACCESS
4 true true true NO ACCESS
5 true true true NO ACCESS
6 true true true NO ACCESS
7 true true true NO ACCESS
8 true true true NO ACCESS
9 true true true NO ACCESS
10 true true true NO ACCESS
11 true true true NO ACCESS
12 true true true NO ACCESS
13 true true true NO ACCESS
14 true true true NO ACCESS
15 true true true NO ACCESS
16 true true true NO ACCESS
17 true true true NO ACCESS

Manually set the password 'mEke5lpiBDTcm' failed:
ubuntu@actual-osprey:~$ sudo ipmitool user set password 3
Password for user 3:
Password for user 3:
IPMI command failed: Unknown (0x82)
Set User Password command failed (user 3)

Manually set the password 'mEke5lpiBDTcm?' succeed, the password follows the password requirement mentioned in bug 1621175:
ubuntu@actual-osprey:~$ sudo ipmitool user set password 3
Password for user 3:
Password for user 3:
Set User Password command successful (user 3)
ubuntu@actual-osprey:~$

After I disabled the password complexity check in iBMC, the node is commissioned successfully: http://paste.ubuntu.com/25066284/. MAAS is able to set up the power type with 'maas' user successfully during enlistment.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.