Juju makes wrong network configuration when adding physical machine

[Dongwon Cho]

Juju makes wrong network configuration as follow when adding physical machine.

auto lo
iface lo inet loopback
    dns-nameservers 10.10.200.2
    dns-search example.com

iface eth0 inet manual

auto juju-br0
iface juju-br0 inet static
    bridge_ports eth0
    gateway 10.10.200.1
    address 10.10.200.3/24
    mtu 1500

auto juju-br0.101
iface juju-br0.101 inet static
    address 192.168.101.3/24
    vlan-raw-device eth0
    mtu 9000
    vlan_id 101

auto juju-br0.102
iface juju-br0.102 inet static
    address 192.168.102.3/24
    vlan-raw-device eth0
    mtu 9000
    vlan_id 102

auto juju-br0.232
iface juju-br0.232 inet manual
    vlan-raw-device eth0
    mtu 9000
    vlan_id 232

I think on the 'eth0' interface, there should be 'auto eth0' so that 'eth0' can be up automatically when the machine starts.
For 'vlan-raw-device', it should be 'juju-br0' not 'eth0' since each of vlan interfaces is from 'juju-br0'.
So I modified the configuration as follow and it works well for me.
(I do not mention about the MTU problem here because it is already reported by others.)

auto lo
iface lo inet loopback
    dns-nameservers 10.10.200.2
    dns-search example.com

auto eth0
iface eth0 inet manual
    mtu 9000

auto juju-br0
iface juju-br0 inet static
    bridge_ports eth0
    gateway 10.10.200.1
    address 10.10.200.5/24
    mtu 9000

auto juju-br0.101
iface juju-br0.101 inet static
    address 192.168.101.5/24
    vlan-raw-device juju-br0
    mtu 9000
    vlan_id 101

auto juju-br0.102
iface juju-br0.102 inet static
    address 192.168.102.5/24
    vlan-raw-device juju-br0
    mtu 9000
    vlan_id 102

auto juju-br0.232
iface juju-br0.232 inet manual
    vlan-raw-device juju-br0
    mtu 9000
    vlan_id 232

$ dpkg -l | egrep -i 'maas|juju'
ii juju-core 1.25.3-0ubuntu1~14.04.1~juju1 amd64 Juju is devops distilled - client
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Andrew McDermott (frobware)]

Please could you attach all /etc/network/interfaces* files. Directories too. Thanks.

[Dongwon Cho (dongwoncho)]

This is the current configuration I am working with.

[Anastasia (anastasia-macmood)]

Networking has changed dramatically on both Juju and MAAS since the time this bug is reported.

Could you please clarify if you experiencing this with later versions?

Feel free to re-open the bug including the updated information requested in comment #1.

Thank you for your patience!

[Dongwon Cho (dongwoncho)]

I will.
Thank you for your efforts!

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]