VLANs on an unconfigured parent device error with "cannot set link-layer device addresses of machine "0": invalid address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Dimiter Naydenov |
Bug Description
I have the following /e/n/i:
ubuntu@
auto lo
iface lo inet loopback
dns-nameservers 10.17.20.200
dns-search maas19
iface eth0 inet manual
auto br-eth0
iface br-eth0 inet static
address 10.17.20.212/24
gateway 10.17.20.1
mtu 1500
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
dns-nameservers 10.17.20.200
auto eth1
iface eth1 inet manual
mtu 1500
auto eth2
iface eth2 inet manual
mtu 1500
auto eth3
iface eth3 inet manual
mtu 1500
iface eth1.16 inet manual
address 10.245.184.100/24
mtu 1500
vlan_id 16
vlan-raw-device eth1
auto br-eth1.16
iface br-eth1.16 inet static
address 10.245.184.100/24
mtu 1500
bridge_ports eth1.16
bridge_stp off
bridge_maxwait 0
iface eth1.17 inet manual
address 10.245.187.100/24
mtu 1500
vlan_id 17
vlan-raw-device eth1
auto br-eth1.17
iface br-eth1.17 inet static
address 10.245.187.100/24
mtu 1500
bridge_ports eth1.17
bridge_stp off
bridge_maxwait 0
so the VLANS (16 and 17) are on eth1 but eth1 is unconfigured (i.e., "manual"). With this setup I get the following error repeated:
2016-04-06 10:58:39 ERROR juju.worker.
This should be a valid configuration as eth1 is auto so can pass traffic.
Changed in juju-core: | |
status: | New → Triaged |
Changed in juju-core: | |
milestone: | none → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0.0 |
Changed in juju-core: | |
milestone: | 2.0.0 → 2.0-beta8 |
Changed in juju-core: | |
milestone: | 2.0-beta8 → 2.0-beta9 |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Dimiter Naydenov (dimitern) |
Changed in juju-core: | |
milestone: | 2.0-beta9 → 2.0-beta10 |
Changed in juju-core: | |
milestone: | 2.0-beta10 → 2.0-beta11 |
Changed in juju-core: | |
milestone: | 2.0-beta11 → 2.0-beta12 |
Changed in juju-core: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
tags: | added: 2.0 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0-beta16 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta16 → none |
milestone: | none → 2.0-beta16 |
Changed in juju: | |
status: | In Progress → Triaged |
Changed in juju: | |
milestone: | 2.0-beta16 → 2.0-beta17 |
tags: | added: 4010 cpec |
Changed in juju: | |
milestone: | 2.0-beta17 → 2.0-beta18 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.0-beta18 → 2.0-rc1 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
It's possible to workaround this issue by ensuring that a VLANs' parent device is always configured with an address.