Bionic commissioning fails looking for wrong interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Andres Rodriguez | ||
2.3 |
Fix Released
|
High
|
Andres Rodriguez |
Bug Description
MAAS version 2.3.0 (6434-gd354690-
Commissioning a node with Bionic fails looking for the wrong interface:
Device "enp47s0f" does not exist.
Traceback (most recent call last):
File "/tmp/user_
dhcp_
File "/tmp/user_
iface for iface in configured_ifaces if has_ipv4_
File "/tmp/user_
iface for iface in configured_ifaces if has_ipv4_
File "/tmp/user_
output = check_output(('ip', '-4', 'addr', 'list', 'dev', iface))
File "/usr/lib/
**kwargs)
File "/usr/lib/
output=stdout, stderr=stderr)
subprocess.
Where the correct interface should be 'enp47s0f0' or 'enp47s0f1' as per the LSHW:
...
<node id="network:0" disabled="true" claimed="true" class="network" handle=
...
and
...
<node id="network:1" claimed="true" class="network" handle=
...
Commissioning with Xenial on the same node passes without issue.
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 129 lines (+61/-30)2 files modifiedsrc/provisioningserver/refresh/node_info_scripts.py (+5/-4)
src/provisioningserver/refresh/tests/test_node_info_scripts.py (+56/-26)
- MAAS Lander: Needs Fixing
- Mike Pontillo (community): Approve
-
Diff: 129 lines (+61/-30)2 files modifiedsrc/provisioningserver/refresh/node_info_scripts.py (+5/-4)
src/provisioningserver/refresh/tests/test_node_info_scripts.py (+56/-26)
Changed in maas: | |
milestone: | none → 2.4.0beta2 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
status: | Incomplete → Confirmed |
Changed in maas: | |
status: | Confirmed → In Progress |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Hi Michael,
Is this still an issue? I've been unable to reproduce this issue.