We should get a bug following this. But essentially Bionic changed how networking configuration is being done, from /etc/network/interfaces to /etc/netplan/*.yaml files.
When we started implementing support for netplan, they hadn't finished support for bonds, so we didn't implement support for reading bonds and configuring them. They have since finished supporting bonds in netplan, and we need to update our support for netplan to include bonds. While we *could* just not past "strict" to the yaml library, I think the net result of that would not be positive, because we might try to create configurations not being aware of part of your network. On Tue, Apr 17, 2018 at 10:46 AM, Vidmantas Rinkevičius < vidmantas.rinkevic...@vgtu.lt> wrote: > Hi, > > During openstack deployment juju gives error on all lxd containers. > > Example: > > sudo juju status > > 3/lxd/0 down pending bionic bridge activation error: > yaml: unmarshal errors: > line 7: field bonds not found in struct netplan. > > yaml: > > openstack-dashboard: > annotations: > gui-x: '500' > gui-y: '-250' > charm: cs:~openstack-charmers-next/bionic/openstack-dashboard > num_units: 1 > bindings: > website: web > options: > openstack-origin: distro-proposed > to: > - lxd:3 > > > I am deploying 18.04 and I use network spaces. > > Any ideas why this error occurs? > > > > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
