smartctl-validate test runs even when explicitly removed from commissioning step
Bug #1964024 reported by
David A. Desrosiers
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Caleb Ellis | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
As titled, when commissioning machines, if you explicitly remove (uncheck) the smartctl-validate unit test, it runs anyway, regardless of whether it's enabled or not.
This presents a larger problem of triggering race conditions with concurrent commissioning, where multiple smartctl-validate tests report their success/failure back to regiond, and cause race conditions, leading to commissioning failures.
Reducing the number nodes requested to commission in parallel reduces the impact of these failures, but it's still non-zero.
When tests are disabled, they should not run at all, including smartctl-validate.
Changed in maas: | |
milestone: | none → next |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas-ui: | |
importance: | Undecided → Unknown |
Changed in maas-ui: | |
status: | New → Fix Released |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
assignee: | nobody → Caleb Ellis (caleb-ellis) |
Changed in maas: | |
milestone: | 3.3.0 → 3.3.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There seem to be two issues: 1) disabling scripts has no effect, and 2) smartctl-validate causes issues. We will investigate both problems.