Commissioning with a Saucy image sets node status to "Failed tests"
Bug #1237364 reported by
Raphaël Badin
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Andres Rodriguez | ||
maas (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
I commissioned an amd64 node with a Precise commissioning image without problem. When trying to commission the same node using a Saucy image, the node failed commissioning and was marked "Failed tests" (the node's page reported: "failed [3/5] ( 00-maas-01-lshw 00-maas-
This is using the lab so should be easy to reproduce/
Related branches
lp:~andreserl/maas/maas_saucy_fix_commissioning
- Andres Rodriguez (community): Approve
- Raphaël Badin (community): Approve
- Gavin Panella (community): Approve
-
Diff: 33 lines (+10/-2)2 files modifiedsrc/metadataserver/models/commissioningscript.py (+5/-0)
src/metadataserver/models/tests/test_commissioningscript.py (+5/-2)
Changed in maas: | |
importance: | High → Critical |
summary: |
- Commissioning with a Saucy image failed. + Commissioning with a Saucy image sets node status to "Failed tests" |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
status: | Triaged → In Progress |
Changed in maas (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
milestone: | none → 13.10 |
status: | Fix Released → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I can confirm that this is only happening with Saucy. I commissioned the same node successfully using Precise, Quantal and Raring.