juju-br0 was reintroduced in 1.23.3 as the default behavior in MAAS, unless the "address-allocation" feature flag is enabled.
AIUI the juju-br0 "swallows" the "interface-mtu" DHCP setting coming from MAAS. It doesn't happen when eth0 is not bound to juju-br0. So it looks like this is a pre-existing issue since for ever.
I'm open to suggestions how Juju can work around the issue (e.g. by generating a slightly different /etc/network/interfaces file with the juju-br0 definition and/or brctl commands).
juju-br0 was reintroduced in 1.23.3 as the default behavior in MAAS, unless the "address- allocation" feature flag is enabled.
AIUI the juju-br0 "swallows" the "interface-mtu" DHCP setting coming from MAAS. It doesn't happen when eth0 is not bound to juju-br0. So it looks like this is a pre-existing issue since for ever.
I'm open to suggestions how Juju can work around the issue (e.g. by generating a slightly different /etc/network/ interfaces file with the juju-br0 definition and/or brctl commands).