MAAS should prevent deploying nodes with PXE interface 'unconfigured' (or all NIC's as 'Unconfigured')
Bug #1513095 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Lee Trager | ||
Bug Description
MAAS allows users deploy a machine that have the PXE interface as 'Unconfigured' as well as deploying a node with *ALL* NIC's as 'Unconfigured'.
Where we saw it it was a node with 2 NIC's that were made bond0, and on deployment, the bond0 for the 'Ip Address' field, it was 'Unconfigured'.
MAAS allowed the user to deploy, but after deployment, it obviously failed to contact metadta sever because no NIC configured.
Related branches
lp:~ltrager/maas/start_only_with_configured_nic
- Andres Rodriguez (community): Needs Information
- Blake Rouse (community): Approve
-
Diff: 157 lines (+44/-1)5 files modifiedsrc/maasserver/models/node.py (+18/-0)
src/maasserver/models/tests/test_node.py (+15/-1)
src/maasserver/static/partials/node-details.html (+7/-0)
src/maasserver/websockets/handlers/node.py (+1/-0)
src/maasserver/websockets/handlers/tests/test_node.py (+3/-0)
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| milestone: | none → 1.9.0 |
| tags: | added: networking ui |
| Changed in maas: | |
| assignee: | nobody → Lee Trager (ltrager) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Jared Baker (shubjero) wrote | #2 |
To post a comment you must log in.
MAAS should make sure that at lease one interface can communicate back to MAAS. I don't know if it has to be the PXE interface.