[enhancement] If a disk doesn't support SMART, the test shouldn't pass

Bug #1760919 reported by Dean Henrichsmeyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Lee Trager

Bug Description

If you run the smartctl-validate script on a node with disks that don't support SMART, the test will pass even though the output clearly says

INFO: Veriying SMART support for the following drive: /dev/sdb
INFO: Running command: sudo -n smartctl --all /dev/sdb
INFO: Unable to run test. The following drive does not support SMART: /dev/sdb

I know it's dangerous to try and interpret results but we should definitely sort that for tests that we ship with MAAS. It gives a false sense of security that things are fine when in fact they may not be. In my case I had a failed disk that "passed" the test so I assumed it was good when in fact it didn't even run.

Related branches

summary: - If a disk doesn't support SMART, the test shouldn't pass
+ [enhancement] If a disk doesn't support SMART, the test shouldn't pass
Changed in maas:
milestone: none → 2.4.x
importance: Undecided → Medium
status: New → Triaged
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
Changed in maas:
milestone: 2.4.x → 2.4.0beta2
Lee Trager (ltrager)
Changed in maas:
status: Triaged → In Progress
Revision history for this message
Lee Trager (ltrager) wrote :

The related branch adds a new skipped status for ScriptResults. All SMART tests now set their status to skipped if SMART is unsupported. This will not effect the status of the node but will be visible in the UI in the hardware tests tab.

Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.