Commissioning with jammy fails on amd64 machines

Bug #1967322 reported by Diego Mascialino
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
3.2
Fix Released
High
Christian Grabowski

Bug Description

Using jammy image to commissioning machines fails on our amd64 ones:

smartctl-validate datails for opelt

output combined shows:

```
Unable to run 'smartctl-validate': Storage device 'PERC H730P Mini' with serial '61866da06e5723001f5b3a6e0ff3e538' not found!

This indicates the storage device has been removed or the OS is unable to find it due to a hardware failure. Please re-commission this node to re-discover the storage devices, or delete this device manually.

Given parameters:
{'storage': {'argument_format': '{path}', 'type': 'storage', 'value': {'id': 14, 'id_path': '/dev/disk/by-id/wwn-0x61866da06e5723001f5b3a6e0ff3e538', 'model': 'PERC H730P Mini', 'name': 'sda', 'serial': '61866da06e5723001f5b3a6e0ff3e538'}}}

Discovered storage devices:
[{'name': 'sda', 'model': 'PERC_H730P_Mini', 'serial': '0038e5f30f6e3a5b1f0023576ea06d86', 'maj:min': '8:0', 'model_enc': 'PERC H730P Mini'}]
Discovered interfaces:
{'18:66:da:6d:fb:3c': 'eno3'}
```

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → High
no longer affects: maas
Revision history for this message
Christian Grabowski (cgrabowski) wrote :

Is this happening on all amd64 machines in the lab? I am able to commission using an amd64 VM successfully, as well as a physical amd64 with a single nvme drive.

Revision history for this message
Diego Mascialino (dmascialino) wrote :

Almost all of the amd64 machines in the lab (the only exception is `squier`).

Please see the attached screenshot, and let me know if I can help you on debugging this issue in our lab.

Revision history for this message
Gabriel Samfira (gabriel-samfira) wrote :

This might be related to: https://github.com/canonical/lxd/issues/12209

I built the "machine-resources" (https://github.com/maas/maas/tree/master/src/host-info) binaries with the fix included, mounted it over the snap binaries:

mount -o bind /root/machine-resources /snap/maas/<SNAP_ID>/usr/share/maas/machine-resources

and restarted maas with:

snap restart maas

After which in my case at least, it worked.

Revision history for this message
Gabriel Samfira (gabriel-samfira) wrote :

To build the "host-info" binaries using the fix in that PR, you will need golang and git installed. Then you can run:

git clone https://github.com/maas/maas.git
cd maas/src/host-info/
go get github.com/canonical/lxd@6433343602f5df2fe40ac146103718c7a767fd6f
make

in your current folder you will have the "bin" folder with the generated binaries. Copy this folder to your MAAS machine and run the above mentioned mount command. In the previous comment, I copied the "bin" folder to "/root/machine-resources" on my MAAS machine.

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.