** No longer affects: util-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
** Changed in: maas
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Changed in: maas/2.7
Importance: Undecided => Critical
** Changed in: maas/2.7
Assignee: (unassigned) => Lee Trager (ltrager)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387605
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387603
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/387604
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: lxd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status
** Bug watch added: LXD bug tracker #7665
https://github.com/lxc/lxd/issues/7665
** Changed in: lxd
Status: Fix Released => Unknown
** Changed in: lxd
Remote watch: LXD bug tracker #7096 => LXD bug tracker #7665
** Changed in: maas
Importance: Undecided => High
** Changed in:
I was able to reproduce this bug by emulating an IDE in QEMU device and
running the smartctl-validate test. I have filed an upstream bug as
well.
https://github.com/karelzak/util-linux/issues/1098
** Bug watch added: github.com/karelzak/util-linux/issues #1098
** Also affects: maas/2.8
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a
** Changed in: lxd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: util-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Tags removed: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869116
Title:
smartctl-validate is borked in a recent release
Status in lxd:
Unknown
Rereading my comment above I had a huge typo, I meant to say that the
script output for 18/16 LTS said "the drivers do not support SMART",
rather than use the word RAID, sorry about that confusion!
-cees
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
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
When running previous (18.xx LTS and 16.xx LTS) options in MAAS for
commissioning it skipped the scripts because it said the drives do not
support RAID. Perhaps that ties in with Alberto's comment. I'm not too
familiar with SMART but I'm not sure why the drives don't support it, I
thought they
I spoke with the LXD team and they're passing through the name they get
from the kernel. It seems like this may be a bug that was introduced to
util-linux with RAID devices. I tried running lsblk on Focal against two
NVME drives and I do not see an underscore used in model names.
@cees - Can you
16 matches
Mail list logo
