juju-br0 fails to be up when no gateway is set on interface
Bug #1560331 reported by
Nobuto Murata
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
| juju-core |
Won't Fix
|
High
|
Unassigned | ||
| 1.25 |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
With MAAS 1.9 and Juju 1.25.3, juju-br0 won't be created if there is no gateway in the MAAS PXE network.
[original /etc/network/
====
auto lo
iface lo inet loopback
dns-nameservers 172.16.0.13
dns-search maas
auto eth0
iface eth0 inet static
address 172.16.0.14/24
mtu 1500
====
Revision history for this message
| James Tunnicliffe (dooferlad) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| Changed in juju-core: | |
| importance: | Undecided → High |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | none → 2.0.0 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Won't Fix |
Revision history for this message
| Alexis Bruemmer (alexis-bruemmer) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
provider/
juju_ipv4_
Clearly if there is no default route this won't work. There are plans to bridge everything so this issue will go away in 2.0, but for 1.25 we need to do something. I suggest that if there is only one interface then bridge it. We also need better error reporting.