Comment 9 for bug 1856832

So I've tested a couple scenarios trying to replicate this (see below), but I can't get it to fail.

Scenarios:

 - Testing with just deploying to lxd with lxd-profiles[1]
 - Testing with just deploying to lxd with lxd-profiles within a bundle[2]
 - Testing with deploying to lxd with subordinates[3]

Repeated all of the above with aws and didn't have an issue.

-

So from the logs we can see there is an issue with openvswitch-3 (see below), but working out why the profile didn't apply is strange.

unit-neutron-openvswitch-3 2020-02-06 21:40:26 DEBUG unit.neutron-openvswitch/3.install runner.go:360 A dependency job for openvswitch-switch.service failed. See 'journalctl -xe' for details.

-

Can we get the syslog/lxd logs from machine 3?
Is the hardware the same for all machines or is there any differences?

---------

 1. charm cs:~juju-qa/bionic/lxd-profile
 2. https://github.com/juju/juju/blob/develop/acceptancetests/repository/bundles-lxd-profile.yaml
 3. https://paste.ubuntu.com/p/xdZnGS7TS8/