[2.1] commissioning doesn't find the second address family on the boot interface
Bug #1638589 reported by
LaMont Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
LaMont Jones | ||
Bug Description
Since the changes for Bug#1621507 cause the booting machine to only DHCP for one address family, and commissioning only probes non-boot interfaces, we fail to find the other address family (if present) on the boot interface.
Commissioning should note the fs_host, and probe the pxeboot interface for the other address family, in addition to the non-boot interfaces.
Related branches
lp:~lamont/maas/bug-1638589
- Blake Rouse (community): Approve
-
Diff: 187 lines (+106/-16)2 files modifiedsrc/provisioningserver/refresh/node_info_scripts.py (+31/-11)
src/provisioningserver/refresh/tests/test_node_info_scripts.py (+75/-5)
| Changed in maas: | |
| assignee: | nobody → LaMont Jones (lamont) |
| assignee: | LaMont Jones (lamont) → nobody |
| Changed in maas: | |
| milestone: | none → 2.1.1 |
| tags: | added: maas-ipv6 |
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → LaMont Jones (lamont) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
