Comment 0 for bug 1784834

Juju: 2.4.1
MAAS: 2.3.3
Ubuntu: 18.04 with latest updates

Relatively simple four machine deployment; machines have connectivity via two physical nics, on with two spaces configured, and the second with just a single space configured (see cloud-init-netplan.yaml for provisioned information).

I think I'm seeing a race between juju reworking the base netplan configuration with bridges, and LXD containers being started which results in a lack of bridges to two spaces on some machines (see
juju-98-netplan.yaml).

On machines where I see missing bridges I also see:

ubuntu@node-urey:/etc/netplan$ ls
50-cloud-init.yaml.bak.1533116635 98-juju.yaml 99-juju.yaml.bak.1533116651

vs

ubuntu@node-hippalus:/etc/netplan$ ls
50-cloud-init.yaml.bak.1533116584 98-juju.yaml.bak.1533116791 99-juju.yaml 99-juju.yaml.bak.1533116764
98-juju.yaml.bak.1533116618 98-juju.yaml.bak.1533116845 99-juju.yaml.bak.1533116602 99-juju.yaml.bak.1533116818
98-juju.yaml.bak.1533116686 98-juju.yaml.bak.1533116897 99-juju.yaml.bak.1533116653 99-juju.yaml.bak.1533116871
98-juju.yaml.bak.1533116738 98-juju.yaml.bak.1533116954 99-juju.yaml.bak.1533116712 99-juju.yaml.bak.1533116925

on one where the bridges have been configured (see juju-99-netplan.yaml).