MAAS no longer handling commissioning script processing failures

Bug #1879416 reported by Lee Trager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Lee Trager
2.7
High
Lee Trager

Bug Description

Prior to MAAS 2.7 MAAS collected commissioning data from multiple scripts. If there was a failure processing the output of a commissioning script only that data would be missing. If a commissioning script failed to process testing wouldn't run.

MAAS 2.7+ now silently ignores commissioning failures making them look like test failures. LP:1878923 and LP:1878643 were both reported as smartctl-validate failures when they were really errors with processing 50-maas-01-commissioning.

Commissioning script failures need to be properly reported and testing should not run if a commissioning failure is detected.

Related branches

Lee Trager (ltrager)
Changed in maas:
milestone: none → 2.8.0rc1
Lee Trager (ltrager)
Changed in maas:
assignee: Lee Trager (ltrager) → nobody
status: In Progress → New
importance: High → Undecided
Lee Trager (ltrager)
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
importance: Undecided → High
status: New → In Progress
Changed in maas:
status: In Progress → Fix Committed
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers