real Maas—real juju–Production system testing -----no vm or lxd or snap
juju connects or attempts to connect through the wrong address
maas server is on xxx.xxx.15.205 but juju tries to connect to xxx.xxx.0.117
bootstrapping begins at xxx.xxx.15.205:5240/MAAS. everything works great and then, the process times out because of where juju tries to connect.
I maybe wrong, but it looks like MAAS is not routing traffic from xxx.xxx.15.205 to xxx.xxx.0.117 and placing the client on the xxx.xxx.0.1, the MAAS dhcp side does not work" it does not communicate with MAAS at the xxx.xxx.15.205"
Creating Juju controller “maas-controller” on maas-cloud/default
Looking for packaged Juju agent version 2.8.4 for amd64
Launching controller instance(s) on maas-cloud/default…
- xaf4rg (arch=amd64 mem=4G cores=2)
Installing Juju agent on bootstrap instance
Fetching Juju Dashboard 0.2.0
Waiting for address
Attempting to connect to 192.168.0.117:22