I've subscribed field critical.
We worked around this issue with the following:
# from unit sudo ip link add name br-prov type bridge sudo ip link set br-prov up sudo ip link set bond1 master br-prov
# From the unit sudo mkdir /etc/network/interfaces.d sudo apt install ifupdown # needed package
# From the infra node juju run -u neutron-gateway/<unit-id> hooks/config-changed
However, this causes issues with Juju as juju checks /sbin/ifup when deciding to use default network interfaces or netplan for bridging when deploying lxds (https://github.com/juju/juju/blob/d59b8637e150943cb987a8194addbdc116746b63/container/broker/instance_broker.go#L125).
To work around this, we have temporarily uninstalled ifupdown (removing /sbin/ifup) and this allows juju to deploy lxds correctly, creating necessary bridges.
What would the recommended workaround for this be?
I've subscribed field critical.
We worked around this issue with the following:
# from unit
sudo ip link add name br-prov type bridge
sudo ip link set br-prov up
sudo ip link set bond1 master br-prov
# From the unit interfaces. d
sudo mkdir /etc/network/
sudo apt install ifupdown # needed package
# From the infra node gateway/ <unit-id> hooks/config- changed
juju run -u neutron-
However, this causes issues with Juju as juju checks /sbin/ifup when deciding to use default network interfaces or netplan for bridging when deploying lxds (https:/ /github. com/juju/ juju/blob/ d59b8637e150943 cb987a8194addbd c116746b63/ container/ broker/ instance_ broker. go#L125).
To work around this, we have temporarily uninstalled ifupdown (removing /sbin/ifup) and this allows juju to deploy lxds correctly, creating necessary bridges.
What would the recommended workaround for this be?