deploy openstack base bundle failed with lxd error: incomplete DNS config found, discovering host's DNS config

[hshtel]

I am trying to deploy openstack base bundle with juju/maas. as described in this blog http://blog.naydenov.net/2015/11/deploying-openstack-on-maas-1-9-with-juju-network-setup/

please check below from my test and advise what is wrong?

all the the lxd machines that juju create are down with this error:
```
cannot start instance for machine "2/lxd/2": acquiring LXD image: no matching image found
```

juju debug-log has these errors related to DNS which I think is the cause to my problem:
```
machine-1: 09:39:24 WARNING juju.provisioner no name servers supplied by provider, using host's name servers.
machine-1: 09:39:24 WARNING juju.provisioner no search domains supplied by provider, using host's search domains.
machine-1: 09:39:24 WARNING juju.provisioner incomplete DNS config found, discovering host's DNS config
machine-0: 09:39:43 WARNING juju.provisioner failed to start machine 0/lxd/2 (acquiring LXD image: no matching image found), retrying in 10s (7 more attempts)
```
juju machines returns below:

```
Machine State DNS Inst id Series AZ Message
0 started 192.168.50.2 os-compute1 bionic default Deployed
0/lxd/0 down pending bionic no matching image found
0/lxd/1 down pending bionic no matching image found
0/lxd/2 down pending bionic no matching image found
1 started 192.168.50.3 os-compute2 bionic default Deployed
1/lxd/0 down pending bionic no matching image found
1/lxd/1 down pending bionic no matching image found
1/lxd/2 down pending bionic no matching image found
2 started 192.168.50.4 os-compute3 bionic default Deployed
2/lxd/0 down pending bionic no matching image found
2/lxd/1 down pending bionic no matching image found
2/lxd/2 down pending bionic no matching image found
3 started 192.168.50.5 os-compute4 bionic default Deployed
3/lxd/0 down pending bionic no matching image found
3/lxd/1 down pending bionic no matching image found
3/lxd/2 down pending bionic no matching image found
```

below is my environment:

juju version: 2.5.4-bionic-amd64

MAAS version: 2.5.2

openstack nodes are VMs on ESXi6.5 and all vSwitch were configured to allow Allow promiscuous mode, forged transmits and MAC changes.

maas network interface configuration, and maas fabrics and spaces are attached below.

[Richard Harding (rharding)]

We had a user hitting this and found that the machine couldn't get the linux container images from the cloud-images.ubuntu.com. Turns out there was a snort rule that was blocking the urls. Testing was to verify if from a machine you could manually launch a lxc container and if not working through what was blocking it up.

[Joseph Phillips (manadart)]

We have observed this behaviour on other MAAS deployments, where things like firewall rules can prevent the MAAS hosts from accessing image streams for the containers. One particular culprit was Snort (https://www.snort.org/).

The thing to try is "lxc launch ..." on one of the hosts and chase down where in your environment the traffic is being blocked.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]