Comment 12 for bug 1856832

I can replicate the issue with the bundle from https://bugs.launchpad.net/juju/+bug/1856832/comments/7 on a MAAS cloud and an Openstack cloud.

- On the MAAS cloud the problem occurred on 3/4 neutron-openvswitch units
- On the Openstack cloud the problem occured on 1/4 neutron-openvswitch units.

I can't replicate the issue with the juju-qa charm bundle (https://paste.ubuntu.com/p/xdZnGS7TS8/) on either cloud.

My understanding is that
- juju allocates the machine,
- then the lxd container machine, juju will merge this with any other relevant lxd profiles that apply to the applications in the lxd machines and apply them?
- applies the primary charm (nova-compute)
- applies the applies the subordinate charm (neturon-openvswitch), and by virtue of the charm having specified an 'lxd-profile.yaml' in its base, juju will merge this with any other relevant lxd profiles that apply to the applications in the lxd machines and apply them?

Is there any other interaction necessary on the part of the charm?