MAAS

ScriptResults are not always aborted when failure is detected

Bug #1851620 reported by Lee Trager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Lee Trager
MAAS 2.7.0b1

Bug Description

While investing another bug I caused maas-run-remote-scripts to fail. This was reported and caused the machine to go into failed testing but the test that was running did not have its status changed to aborted.

Related branches

~ltrager/maas:lp1851620
Alberto Donato (community): Approve
Diff: 49 lines (+19/-1)
2 files modified
src/metadataserver/api.py (+13/-1)
src/metadataserver/tests/test_api.py (+6/-0)
MAAS Lander (maas-lander)
Changed in maas:
status: In Progress → Fix Committed
Adam Collard (adam-collard)
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.
Subscribing...

Other bug subscribers

Remote bug watches

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