Comment 25 for bug 1833604

Ok, so diving into the storage side of things, the fields which aren't filled are:

 - device_path
 - firmware_version
 - model
 - serial
 - wwn

I did some poking around and came to the conclusion that it is correct for them all to be empty.
device_path was the weirdest one to find empty but it is correct as there is no by-id entries for those block devices. I've sent a change to LXD to make that field optional so it doesn't show up as empty in the raw JSON output.

The others are all assuming a physical device with a fixed vendor, model, firmware and unique identifier. None of that applies here as we're dealing with a virtual block device made from some amount of memory coming from a variety of modules. Those modules could in theory be from different models and vendors, so even if I could track them down, we wouldn't get a nice answer for those.

That concludes my investigation. At least on Ubuntu 20.04, the system behaves as I would expect.
We are properly seeing the block devices created and the memory we report matches the memory configuration available to the system (volatile).