Event log should always include a reason why a node was marked Failed Deployment
Bug #1604987 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Unassigned | ||
| 2.0 |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Right now, when a node fails deployment, the event log does not report why. We just get a description like this:
"description": "From 'Deploying' to 'Failed deployment'",
That's not helpful at all when debugging, or when using automated tools to identify common failures. We still have to go and dig into the MAAS logs to get a clue of why the node failed to deploy.
This is with 2.0rc2
Related branches
lp:~andreserl/maas/lp1604962_lp1604987
- Andres Rodriguez (community): Approve
- Gavin Panella (community): Approve
-
Diff: 291 lines (+85/-40)7 files modifiedsrc/maasserver/models/node.py (+33/-20)
src/maasserver/models/tests/test_node.py (+12/-3)
src/maasserver/rpc/nodes.py (+1/-1)
src/maasserver/status_monitor.py (+1/-1)
src/metadataserver/api.py (+18/-12)
src/metadataserver/tests/test_api_status.py (+5/-3)
src/provisioningserver/events.py (+15/-0)
lp:~andreserl/maas/lp1604962_lp1604987_2.0
- Andres Rodriguez (community): Approve
-
Diff: 306 lines (+89/-40)8 files modifieddocs/changelog.rst (+4/-0)
src/maasserver/models/node.py (+33/-20)
src/maasserver/models/tests/test_node.py (+12/-3)
src/maasserver/rpc/nodes.py (+1/-1)
src/maasserver/status_monitor.py (+1/-1)
src/metadataserver/api.py (+18/-12)
src/metadataserver/tests/test_api_status.py (+5/-3)
src/provisioningserver/events.py (+15/-0)
lp:~andreserl/maas/packaging_rc3
- Andres Rodriguez (community): Approve
-
Diff: 90 lines (+54/-6)2 files modifieddebian/changelog (+44/-0)
debian/maas-region-controller.postinst (+10/-6)
| Changed in maas: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| no longer affects: | maas/1.9 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
