LXD recognizes video encoder as NVMe drive

[Simon Fels]

While post processing the commissioning results MAAS fails with

kamek.maas(be6qpq): commissioning script '50-maas-01-commissioning' failed during post-processing.

See the attached log of the 50-maas-01-commissioning script.

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.

[dann frazier (dannf)]

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.

[Adam Collard (adam-collard)]

The traceback that causes the script to 'fail' is when MAAS tries to process the results from the machine-resources binary - https://paste.ubuntu.com/p/RgW7y8qQ3q/

django.core.exceptions.ValidationError: {'size': ['Partition cannot be saved; not enough free space on the block device.']}

I think we're safe to say that Simon's theory is holding.

[Lee Trager (ltrager)]

MAAS now gets all of its commissioning information from LXD. Could you also file this bug against LXD and associate it with this bug?

[Lee Trager (ltrager)]

What size is the disk that is showing up? I just remembered MAAS has a global variable MIN_BLOCK_DEVICE_SIZE which is currently set to 4MB. Any block device which is smaller than 4MB is ignored. 4MB was enough to fit a partition table but maybe things have changed.

[Simon Fels (morphis)]

It's about ~300MB

[Lee Trager (ltrager)]

I suspect something else is going on here then. A partition table should absolutely be able to fit within a 300MB disk. Can you post the output of 50-maas-01-commissioning?

[Simon Fels (morphis)]

Looks like I forgot to attach it with the initial report. Added it now