bionic LXD containers with more than one space configures multiple default gateways using netplan (xenial/ifupdown does not)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When deploying bionic LXD containers with more than 1 space (e.g. default space + application binding space) multiple default gateways are set. This is not the case with xenial LXD containers.
Looking at the LXD configuration, we see that the netplan stanza outputs gateway4 for each interface but the ifupdown section only outputs gateway for one interface. It is expected this gateway will try to match the hosts default gateway interface if possible (Since Pull #8140).
Tested on Juju 2.4.3-cosmic-amd64
lxd config show excerpt:
==Netplan ==
version: 2
ethernets:
eth0:
match:
- 100.64.0.59/24
mtu: 9000
eth1:
match:
- 100.64.1.44/24
mtu: 9000
== ifupdown ==
auto lo {eth00_
iface lo inet loopback
dns-search maas
iface {eth00_
address 100.64.0.59/24
gateway 100.64.0.254
mtu 9000
iface {eth00_
address 100.64.1.44/24
mtu 9000
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5-beta1 |
Changed in juju: | |
milestone: | 2.5-beta1 → 2.5-beta2 |
Changed in juju: | |
milestone: | 2.5-beta2 → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
Removing from a milestone as this work will not be done in 2.5 series.