Unhelpful error when re-enlisting a previously enlisted node
Bug #1308292 reported by
James Troup
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Raphaël Badin | ||
Bug Description
While trying to commission a node, I got the following:
=== Wed, 16 Apr 2014 00:27:22 +0000: successfully enlisted to 'http://
{"mac_addresses": ["One or more MAC addresses is invalid.
This node has actually been commissioned previously; successfully,
even. The only change I've made since then is swapping PXE from an
on-board 1Gb NIC (eth0) to a 10Gb NIC (eth2).
This is with maas 1.4+bzr1693+
Related branches
lp:~rvb/maas/form-error-msg-bug-1308292
- Jeroen T. Vermeulen (community): Approve
-
Diff: 360 lines (+159/-24)8 files modifiedsrc/maasserver/api.py (+2/-2)
src/maasserver/fields.py (+43/-9)
src/maasserver/forms.py (+34/-5)
src/maasserver/tests/test_api_enlistment.py (+5/-2)
src/maasserver/tests/test_api_macaddress.py (+1/-1)
src/maasserver/tests/test_api_node.py (+3/-3)
src/maasserver/tests/test_fields.py (+31/-0)
src/maasserver/tests/test_forms.py (+40/-2)
Revision history for this message
| James Troup (elmo) wrote | #2 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| summary: |
- 'One or more MAC addresses is invalid.' when commissioning + Unhelpful error when re-commissioning a previously commissioned node |
| summary: |
- Unhelpful error when re-commissioning a previously commissioned node + Unhelpful error when re-enlisting a previously enlisted node |
Revision history for this message
| Raphaël Badin (rvb) wrote | #3 |
| Changed in maas: | |
| milestone: | none → 14.10 |
| assignee: | nobody → Raphaël Badin (rvb) |
| status: | Triaged → In Progress |
Revision history for this message
| Raphaël Badin (rvb) wrote | #4 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Right, so, after tcpdumping the traffic between the node and the region controller, I figueed out the problem. When it says invalid, what MAAS means is 'is a duplicate'. I deleted the old version of the node (from when it was PXE booting with eth0) in MAAS and the node was able to successfully declare and commission.
While, once again, there's a element of user error in this bug, at the very least, it'd be nice if the error message was more informative (and didn't consider a 400 response a 'success').