[2.3, HWTv2] Aborting testing goes back into the incorrect state
Bug #1727547 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Newell Jensen |
Bug Description
I had machines that were in a 'Testing' state, but when I aborted them, they went back to 'Ready' State instead of 'Failed testing'. To reproduce:
1. Start testing of two machines in 'Ready' state, for two tests you know they will fail (e.g. internet test but remove internet connectivity).
2. Wait for the machines to go to 'Failed testing'
3. Then run testing again with 'Test hardware' action.
4. While on 'Testing' state, click the 'Abort' action.
5. You will notice machines go back to 'Ready' instead of 'Failed testing'.
Related branches
~newell-jensen/maas:lp1727547
- Blake Rouse (community): Approve
- MAAS Lander: Needs Fixing
- Andres Rodriguez (community): Needs Fixing
-
Diff: 46 lines (+2/-4)3 files modifiedsrc/maasserver/models/signals/nodes.py (+1/-2)
src/maasserver/models/signals/tests/test_nodes.py (+0/-1)
src/maasserver/node_status.py (+1/-1)
Changed in maas: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 2.3.0beta3 |
summary: |
- [2.3] Aborting testing goes back into the incorrect state + [2.3, HWTv2] Aborting testing goes back into the incorrect state |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.