That makes sense based on the other information in this bug.

MAAS sends the test runner a list of storage devices to run hardware
tests on. The test runner uses the model and serial to map to a block
device name. This block device name is passed to the smartctl-validate
script. smartctl-validate uses smartctl to determine if SMART data is
available for the device.

Because the model name differs between lsblk and lxc it can't be looked
up and the test is marked as a failure. The mapping needs to work so
MAAS can pass the block device to to smartctl-validate which knows the
test can be skipped.

** Tags added: champagne

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869116

Title:
  smartctl-validate is borked in a recent release

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/1869116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to