[2.5] Commissioning results in an alias interface automatically created
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
2.4 |
Fix Committed
|
High
|
Mike Pontillo |
Bug Description
I commissioning a machine (which happened to be a VM inside a MAAS deployed Pod), and the interface obtained two different IP addresses during commissioning.
The network commissioning script captured this and created a new interface in the machine with Ready state. The commissioning output for interfaces show:
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens4: <BROADCAST,
link/ether 52:54:00:0f:2d:94 brd ff:ff:ff:ff:ff:ff
inet 10.90.90.225/24 brd 10.90.90.255 scope global ens4
valid_lft forever preferred_lft forever
inet 10.90.90.198/24 brd 10.90.90.255 scope global secondary ens4
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
The resulting machine, please see attached screenshot.
That said, this doesn't seem like an issue isolated to machines inside a pod because I /think/ I've seen this issue in other machines.
Related branches
- Mike Pontillo (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 94 lines (+51/-8)2 files modifiedsrc/maasserver/models/interface.py (+33/-8)
src/maasserver/models/tests/test_interface.py (+18/-0)
- Andres Rodriguez (community): Approve
- MAAS Lander: Approve
-
Diff: 94 lines (+51/-8)2 files modifiedsrc/maasserver/models/interface.py (+33/-8)
src/maasserver/models/tests/test_interface.py (+18/-0)
Changed in maas: | |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Just thinking out loud here, but I'm wondering if this could be related to bug #1749019. I know we've had issues with DHCP IP addresses from the PXE environment not playing well with subsequently- acquired addresses from ISC DHCP, but that's the most recent thing that has changed in this area...