MAAS looks for NICs with kernel module loaded and fall back doesn't check persistent device names
Bug #1519919 reported by
Lee Trager
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Lee Trager | ||
1.9 |
Fix Released
|
High
|
Lee Trager |
Bug Description
When the cluster controller is first installed it scans the host to see which networks the cluster controller is on. This information is sent to the region controller to populate subnets and managed interfaces fields.
When using Xenial in a KVM instance using the virtio auto detection fails and the user is forced to manually enter in all network information.
Related branches
lp:~ltrager/maas/fix_xenial_net_detect
- Mike Pontillo (community): Approve
-
Diff: 121 lines (+28/-14)3 files modifiedsrc/provisioningserver/network.py (+1/-0)
src/provisioningserver/utils/ipaddr.py (+2/-5)
src/provisioningserver/utils/tests/test_ipaddr.py (+25/-9)
lp:~ltrager/maas/fix_xenial_net_detect-1.9
- Lee Trager (community): Approve
-
Diff: 121 lines (+28/-14)3 files modifiedsrc/provisioningserver/network.py (+1/-0)
src/provisioningserver/utils/ipaddr.py (+2/-5)
src/provisioningserver/utils/tests/test_ipaddr.py (+25/-9)
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
importance: | Undecided → High |
summary: |
- MAAS Look for NIC with kernel module loaded and fall back doesn't check - presistent device names + MAAS looks for NICs with kernel module loaded and fall back doesn't + check persistent device names |
Changed in maas: | |
status: | New → Triaged |
status: | Triaged → In Progress |
milestone: | none → next |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
milestone: | next → none |
To post a comment you must log in.