MAAS should not add 'source /etc/network/interfaces.d/*.cfg' to /etc/network/interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
curtin |
New
|
Undecided
|
Unassigned |
Bug Description
Looking at a deployed node I have:
ubuntu@
auto lo
iface lo inet loopback
dns-nameservers 10.11.19.2
dns-search maas19
auto eth0
iface eth0 inet static
gateway 10.11.19.1
address 10.11.19.110/24
mtu 1500
auto eth1
iface eth1 inet static
address 10.11.19.111/24
mtu 1500
auto eth2
iface eth2 inet static
address 10.11.19.113/24
mtu 1500
auto eth3
iface eth3 inet static
address 10.11.19.112/24
mtu 1500
source /etc/network/
and ALSO:
ubuntu@
/etc/network/
`-- eth0.cfg
0 directories, 1 file
ubuntu@
# The primary network interface
auto eth0
iface eth0 inet dhcp
So when the machine boots I start off with a static IP address then get a DHCP address.
This is relatively new behaviour as for a long time the /e/n/i I would get from a MAAS deployed node would not get the 'source' stanza.
This is MAAS 1.9.3:
aim@maas19:~$ dpkg -l |grep maas
ii maas-cli 1.9.3+bzr4577-
ii maas-cluster-
ii maas-common 1.9.3+bzr4577-
ii maas-dhcp 1.9.3+bzr4577-
ii maas-dns 1.9.3+bzr4577-
ii maas-proxy 1.9.3+bzr4577-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.3+bzr4577-
ii python-maas-client 1.9.3+bzr4577-
ii python-
Hi Andrew,
Can you please attach the version of curtin you are using ? This is an issue in curtin.