doesn't detect the subarchitecture xgene-uboot for a HP m400 cartridge

Bug #1918978 reported by Patricia Domingues
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Alberto Donato

Bug Description

I've recommissioned one HP Moonshot 1500 Chassis' m400 cartridge (arm64) and then I could not deploy the system.
Its architecture configuration is `arm64/generic`, but it should be `arm64/xgene-uboot`.

Related branches

Revision history for this message
Patricia Domingues (patriciasd) wrote :

I wasn't able to deploy this system, it got stuck on a PXE boot loop "bug 1918977".
Manually changing its architecture configuration to `arm64/xgene-uboot` - I can successfully deploy this cartridge with Ubuntu Trusty, Xenial and Bionic.

Revision history for this message
Patricia Domingues (patriciasd) wrote :

There's the appropriate mapping of this subarch
"ProLiant m400 Server Cartridge": "arm64/xgene-uboot" on MAAS code.
I wonder if it got broken at some point.

Bill Wear (billwear)
Changed in maas:
status: New → Triaged
Revision history for this message
Alberto Donato (ack) wrote :

What's the output from `show node info <node-id>` on that chassis?

Revision history for this message
dann frazier (dannf) wrote :

hpiLO->show node info c34n1

  c34: #Cartridge 34
    Type: Compute
    Manufacturer: HP
    Product Name: ProLiant m400 Server Cartridge
    Product ID: 721717-B21
    AutoRev: 0A
    Serial Number: CN7505VJ55
    Power: Off
    c34n1: #Node 1
      Node Asset Tag:
      DIMM 1:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 2:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 3:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 4:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 5:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 6:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 7:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      DIMM 8:
        DIMM Capacity: 8 GB
        DIMM Serial Number: 00000000
      NIC 1 MAC Address: 14:58:d0:58:93:92
      NIC 2 MAC Address: 14:58:d0:58:93:93
      HDD 1: # Disk 1
        Firmware: HPS4
        Model: XR0240GEBLU
        Serial Number: 14200EEFA453
        Wear: 0%

hpiLO->

Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

Could you provide logs from commissioning that result in an attempt to deploy arm64/generic subarch?

Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
Revision history for this message
dann frazier (dannf) wrote :

I've attached the output of the 50-maas-01-commissioning script. I'm not sure if that is what you are looking for - if not, can you be specific on how to collect the needed logs?

Changed in maas:
status: Expired → Confirmed
Changed in maas:
status: Confirmed → New
Alberto Donato (ack)
Changed in maas:
milestone: none → 3.3.0
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Alberto Donato (ack) wrote :

During recommissioning, MAAS currently always resets the subarch to generic. We could change this to preserve it, since we only get the arch (not the subarch) from commissioning data.

Alberto Donato (ack)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Alberto Donato (ack)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 3.3.0 → 3.3.0-beta1
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.