Commissioning with jammy fails on amd64 machines
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-
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/
Discovered storage devices:
[{'name': 'sda', 'model': 'PERC_H730P_Mini', 'serial': '0038e5f30f6e3a
Discovered interfaces:
{'18:66:
```
Related branches
- MAAS Lander: Approve
- Adam Collard (community): Approve
-
Diff: 70 lines (+48/-0)2 files modifiedsrc/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+5/-0)
src/metadataserver/user_data/templates/snippets/tests/test_maas_run_remote_scripts.py (+43/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
no longer affects: | maas |
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.