LXD recognizes video encoder as NVMe drive
Bug #1906834 reported by
Simon Fels
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Alexsander de Souza | ||
lxd |
New
|
Undecided
|
Unassigned |
Bug Description
While post processing the commissioning results MAAS fails with
kamek.maas(be6qpq): commissioning script '50-maas-
See the attached log of the 50-maas-
My guess is that it fails because of the listed Netint T408 storage device which is not really one. It's a video encoder card which claims itself to be a NVMe storage device.
Related branches
~alexsander-souza/maas:lp1906834_nvme_too_small_for_booting
Merged
into
maas:master
- MAAS Lander: Approve
- Adam Collard (community): Approve
-
Diff: 1343 lines (+1024/-25)14 files modifiedsrc/maasserver/forms/tests/test_bcache.py (+2/-2)
src/maasserver/forms/tests/test_cacheset.py (+10/-4)
src/maasserver/forms/tests/test_raid.py (+6/-3)
src/maasserver/forms/tests/test_volume_group.py (+2/-2)
src/maasserver/models/node.py (+2/-0)
src/maasserver/models/tests/test_blockdevice.py (+1/-1)
src/maasserver/models/tests/test_filesystem.py (+1/-1)
src/maasserver/models/tests/test_node.py (+17/-5)
src/maasserver/storage_layouts.py (+4/-0)
src/maasserver/testing/factory.py (+8/-2)
src/maasserver/tests/test_node_constraint_filter_forms.py (+9/-3)
src/maasserver/triggers/tests/test_websocket_listener.py (+3/-1)
src/maasserver/websockets/handlers/tests/test_machine.py (+4/-1)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+955/-0)
summary: |
- MAAS fails in post processing of the commissioning results + LXD recognizes video encoder as NVMe drive |
Changed in maas: | |
milestone: | 3.0.0 → 3.0.1 |
Changed in maas: | |
assignee: | nobody → Alexsander de Souza (alexsander-souza) |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | 3.0.1 → 3.2.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Adding a tag w/ kernel_ opts="modprobe. blacklist= nvme" allowed commissioning to complete. Obviously that's just a workaround - and luckily this system doesn't use NVMe for storage. But it is evidence for Simon's theory.