commission failed with MAAS 3.1 when BMC has multiple channels but the first channel is disabled

Bug #1979403 reported by Chuan Li
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Unassigned
3.1
Won't Fix
Undecided
Unassigned
3.2
Fix Released
Medium
Unassigned
3.3
Fix Released
Medium
Alexsander de Souza

Bug Description

One of UA customer can not commission a machine successfully with MAAS 3.1.

The machine has a BMC with 3 LAN channels(3 ports), but only 1 port/channel is enabled(not the first one).

30-maas-01-bmc-config logs are
.....
Unknown section `Lan6_Conf', perhaps another category must be specified (see --category)
Unknown section `Lan6_Conf', perhaps another category must be specified (see --category)
Unknown section `Lan6_Conf', perhaps another category must be specified (see --category)
Unknown section `Lan6_Conf', perhaps another category must be specified (see --category)
.....
ERROR: Unable to determine BMC IP address!
NFO: Loading IPMI kernel modules...
INFO: Checking for HP Moonshot...
INFO: Checking for IPMI...
INFO: IPMI detected!
INFO: Reading current IPMI BMC values...
INFO: Configuring IPMI Lan_Channel...
INFO: Configuring IPMI Lan_Channel_Auth...
INFO: Lan_Channel_Auth settings unavailable!
INFO: Configuring IPMI cipher suite ids...
INFO: Gathering supported cipher suites and current configuration...
INFO: BMC supports the following ciphers - [1, 2, 3, 6, 7, 8, 11, 12, 15, 16, 17]
INFO: Current cipher suite configuration - XXXXXXXXXXXXXXX
INFO: New cipher suite configuration - XXXXXXXXXXXXXXX
INFO: MAAS will use IPMI cipher suite id "17" for BMC communication
WARNING: No K_g BMC key found or configured, communication with BMC will not use a session key!
INFO: Configuring IPMI Serial_Channel...
INFO: Serial_Channel settings unavailable!
INFO: Configuring IPMI SOL_Conf...
INFO: Found existing IPMI user "admin01"!
INFO: Configuring IPMI BMC user "admin01"...
INFO: IPMI user number - User2
INFO: IPMI user privilege level - Administrator
INFO: IPMI Version - LAN_2_0
INFO: IPMI boot type - efi
NFO: Attempting to enable preconfigured static IP on BMC...
INFO: Reading current IPMI BMC values...
INFO: Reading current IPMI BMC values...
INFO: Reading current IPMI BMC values...
INFO: Attempting to enable DHCP on BMC...
INFO: Reading current IPMI BMC values...
INFO: Reading current IPMI BMC values...
......

ii maas-cli 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS client and command-line interface
ii maas-common 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS server common files
ii maas-proxy 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS Caching Proxy
ii maas-region-api 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all Region controller API service for MAAS
ii maas-region-controller 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all Region Controller for MAAS
ii python3-django-maas 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all MAAS server provisioning libraries (Python 3)

power configuration is as below:
- power type: IPMI
- Power driver: LAN_2+0[IPMI 2.0]
- Power boot type: automatic
- IP address: 10.x.x.x
- Power user: maasdeploy
- power password: xxxx
- k_g BMC key: empty
- cipher suite ID: 3- HMAC-SHA1::HMAC-SHA1-96::AES-CBC-128
- Privilege level: operator
- power mac A4:BF:01:AB:CD:EC

I ask customer to dump bmc-config via 'bmc-config -h <ipmi-ip> -p <ipmi-password> -u <ipmi-user> --checkout'
PFA bmc_config_channels-clean

From bmc_config_channels-clean we can see that there is only one Lan_conf section. So bmc-config can not recognize the third channel/port where a static IP configured onto. bmc-config only recognize/grab information from the first channel/port of A BMC.
"
Section Lan_Conf
 IP_Address_Source Use_DHCP
 IP_Address 0.0.0.0
 MAC_Address A4:BF:01:AB:CD:EA
 Subnet_Mask 0.0.0.0
 Default_Gateway_IP_Address 0.0.0.0
 Default_Gateway_MAC_Address 00:00:00:00:00:00
 Backup_Gateway_IP_Address 0.0.0.0
 Backup_Gateway_MAC_Address 00:00:00:00:00:00
EndSection
"

We believe that why 30-maas-01-bmc-config complain "ERROR: Unable to determine BMC IP address"

Tags: sts

Related branches

Revision history for this message
Chuan Li (lccn) wrote :
tags: added: sts
Revision history for this message
Alexsander de Souza (alexsander-souza) wrote :

Please, run the bcm-config command again in verbose mode:
# bmc-config -h <ipmi-ip> -p <ipmi-password> -u <ipmi-user> --checkout --verbose

This mode shows the additional channels settings in `Lan_Conf_Channel_x` sections.

The output should give us an idea about the work required to support multiple channels in MAAS (currently unsupported) and if any workaround is possible.

Changed in maas:
status: New → Incomplete
Revision history for this message
Chuan Li (lccn) wrote :

@alexsander-souza,Hi Alexsander, please check the verbose output bmc_config_verbose-clean

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
Aitelkabous Mohamed (maitelkabous) wrote :

Hello,
We have same issue with Intel server since we upgraded our MAAS to 3.0.
Did you find a solution?

Revision history for this message
Seyeong Kim (seyeongkim) wrote :

@maitelkabous

Hello, Is it possible you can test working branch https://code.launchpad.net/~seyeongkim/maas/+git/maas/+merge/429786 ?

I don't have server which has multiple channel BMC. so Im trying to implement this based on attached output.

Revision history for this message
Seyeong Kim (seyeongkim) wrote :
Changed in maas:
milestone: none → 3.4.0
status: Triaged → Fix Committed
Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

MAAS bug-council:

This fix is desired in MAAS 3.3 and 3.2. Can we send backport MRs? Thanks!

tags: added: bug-council
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

@Seyeong - thanks for the fix. Would you like to propose branches for backporting to 3.3 and 3.2?

tags: removed: bug-council
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.0-beta1
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
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.