Curiously this does not occur when deploying with MAAS+LXD when the underlying machine is a virtual machine as opposed to a physical bare metal one.
That could suggest that the issue indeed is changes in how things are wired/bridged out of the host and/or suggest environmental network issues such as STP.
I see that cloud-init has the capability of managing /etc/hosts already through the `manage_etc_hosts` config key.
I wonder if we could influence this from the charm LXD profile through the use of the `user.vendor-data` knob while awaiting a way to have juju put this into the user-data for us.
Curiously this does not occur when deploying with MAAS+LXD when the underlying machine is a virtual machine as opposed to a physical bare metal one.
That could suggest that the issue indeed is changes in how things are wired/bridged out of the host and/or suggest environmental network issues such as STP.
I see that cloud-init has the capability of managing /etc/hosts already through the `manage_etc_hosts` config key.
I wonder if we could influence this from the charm LXD profile through the use of the `user.vendor-data` knob while awaiting a way to have juju put this into the user-data for us.