Commissioning does not identify interface VLANs on secondary fabrics
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
1.9 |
Fix Released
|
High
|
Mike Pontillo |
Bug Description
install MAAS 1.9 with mutiple interfaces enabled and DHCP through MAAS on different subnet and fabrics.
Commission a node with mutiple interfaces but all attach to same fabric. During investigation found out that not all interfaces are enabled.
could init output http://
commissioning output in MAAS
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: eth0: <BROADCAST,
link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,
link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,
link/ether 52:54:00:06:ff:71 brd ff:ff:ff:ff:ff:ff
but actual ip address after commisoning is as follows:
ubuntu@bootstrap:~$ ip addr
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: eth0: <BROADCAST,
link/ether 52:54:00:f5:af:4c brd ff:ff:ff:ff:ff:ff
inet 10.4.1.70/21 brd 10.4.7.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,
link/ether 52:54:00:d2:df:db brd ff:ff:ff:ff:ff:ff
inet 10.4.9.151/24 brd 10.4.9.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,
link/ether 52:54:00:06:ff:71 brd ff:ff:ff:ff:ff:ff
inet 10.2.66.151/24 brd 10.2.66.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:
valid_lft forever preferred_lft forever
ubuntu@bootstrap:~$
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 195 lines (+70/-27)4 files modifiedsrc/maasserver/models/interface.py (+13/-1)
src/maasserver/models/tests/test_interface.py (+32/-0)
src/maasserver/testing/factory.py (+12/-6)
src/metadataserver/models/commissioningscript.py (+13/-20)
- Blake Rouse (community): Approve
-
Diff: 188 lines (+68/-25)4 files modifiedsrc/maasserver/models/interface.py (+13/-1)
src/maasserver/models/tests/test_interface.py (+32/-0)
src/maasserver/testing/factory.py (+12/-6)
src/metadataserver/models/commissioningscript.py (+11/-18)
summary: |
- maas does not enable all interfaces during commisoning + Commissioning does not resolve interface VLANs on secondary fabrics |
summary: |
- Commissioning does not resolve interface VLANs on secondary fabrics + Commissioning does not identify interface VLANs on secondary fabrics |
Changed in maas: | |
milestone: | none → next |
importance: | Undecided → Critical |
importance: | Critical → High |
assignee: | nobody → Mike Pontillo (mpontillo) |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
milestone: | next → none |
Hi Narinder,
After the machine has fully commissioned, can you do:
dhclient eth2 ?
If eth2 obtains an IP address for a subnet that's on a different fabric, this will be udpated. If there's no IP address obtained from DHCP, then the interface will be added to the same fabric as the PXE interface.