Support arm-storm on HP Moonshot m400

Bug #1714533 reported by David Lawson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

Trying to auto-enlist an m400 cartridge on maas 2.3 fails because, it appears, MaaS can't detect what architecture it is and serve the correct bootloader.

Using NIC1 device
TFTP from server 10.189.128.2; our IP address is 10.189.131.5
Filename 'pxelinux.cfg/default-arm-storm'.
Load address: 0x4000800000
Loading: *
TFTP error: '(b'UNHANDLED', 'Unknown Error [spoink:pid=20874:cmd=GetBootConfig:ask=1d0]')' (0)
Starting again

Enlisting the cartridge by hand and setting the architecture to arm64/xgene-uboot allows the node to PXE and commission.

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

Hi David,

Ok, so can you please provide logs? Also, have you imported all arm images ? Is this arm64 or xgene-uboot ? Hasn't xgene-uboot been dropped already?

Revision history for this message
David Lawson (deej) wrote :

I've no idea frankly, it certainly still exists in the architecture dropdown of the MaaS UI. We're importing all arm64 images. Which logs would you like?

Here's the boot-source-selections list:

$ maas maas-root boot-source-selections read 1
Success.
Machine-readable output follows:
[
    {
        "arches": [
            "amd64",
            "arm64"
        ],
        "release": "xenial",
        "resource_uri": "/MAAS/api/2.0/boot-sources/1/selections/1/",
        "subarches": [
            "*"
        ],
        "id": 1,
        "labels": [
            "*"
        ],
        "os": "ubuntu",
        "boot_source_id": 1
    }
]

And the boot sources themselves:

$ maas maas-root boot-sources read
Success.
Machine-readable output follows:
[
    {
        "updated": "2016-11-29T11:23:43.309",
        "created": "2016-11-29T11:23:43.309",
        "keyring_filename": "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg",
        "id": 1,
        "keyring_data": "",
        "url": "http://images.maas.io/ephemeral-v3/daily/",
        "resource_uri": "/MAAS/api/2.0/boot-sources/1/"
    }
]

Changed in maas:
status: Incomplete → New
tags: added: canonical-is
Revision history for this message
Andres Rodriguez (andreserl) wrote :

David,

As far as I understand, the architecture of this system is an arm-storm, which is not an architecture we have ever enabled or even certified (with Ubuntu).

Can you confirm whether this is standard systems that work with standard arm kernels? Does this need a special kernel? Or is this simply a rename of the hardware?

Changed in maas:
importance: Undecided → Wishlist
milestone: none → next
status: New → Triaged
summary: - Can't auto-enlist HP Moonshot m400
+ Support arm-storm on HP Moonshot m400
tags: added: internal
Revision history for this message
David Lawson (deej) wrote :

The nodes I have deployed are set up as arm64/xgene-uboot with no minimum kernel defined, they're booted with the ga-16.04 kernel, nothing special.

Revision history for this message
David Lawson (deej) wrote :

I'm honestly surprised they haven't been certified, I thought the Moonshots were a partnership project with HP, they certainly have documentation for Ubuntu on their website...

Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
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.