I’m running MAAS in an LXD container, with a KVM VM commissioned in there to host the Juju controller for the MAAS Cloud. I add the MAAS cloud and creds to Juju, and start the bootstrap process with --to sweet-bull.maas (the VM) and bootstrapping gets most of the way through, until it tries to talk to the MAAS API after running the machine configuration script. Output snippet looks like this:
(Reading database ... 66825 files and directories currently installed.) Preparing to unpack .../ubuntu-fan_0.12.10_all.deb ... Unpacking ubuntu-fan (0.12.10) ... Processing triggers for ureadahead (0.100.0-20) ... Setting up ubuntu-fan (0.12.10) ... Created symlink /etc/systemd/system/multi-user.target.wants/ubuntu-fan.service → /lib/systemd/system/ubuntu-fan.service. Processing triggers for systemd (237-3ubuntu10.3) ... Processing triggers for man-db (2.8.3-2) ... Processing triggers for ureadahead (0.100.0-20) ... 5e34daad65322cf751c740b956ed26cb9b47cdc14a38b89cac5f08796ea89f4e /var/lib/juju/tools/2.5-beta1-bionic-amd64/tools.tar.gz f98f377d076dda630d80edc37f6fb6c475cac7f65d1dde4b525128d575db1192 /var/lib/juju/gui/gui.tar.bz2 Installing Juju machine agent 2018-10-18 19:24:16 INFO juju.cmd supercommand.go:56 running jujud [2.5-beta1 gc go1.10] ERROR new environ: Get http://maas-hl:5240/MAAS/api/2.0/version/: dial tcp: lookup maas-hl on 127.0.0.53:53: server misbehaving ERROR failed to bootstrap model: subprocess encountered error code 1
I guess some part of the VM-LXD network is misconfigured, which I’m stepping through now. the VM has connectivity and is getting a valid IP from MAAS. It’s networking is an attachment to the MAAS network.