With /etc/maas/rackd.conf containing maas_url: http://localhost:5240/MAAS, I end up with cloud-config-url=//172.17.16.10/MAAS/metadta/latest/... passed to my system on the command line. This isn't a valid URL and prevents deploy.
Updating rackd.conf to use http://172.17.16.10:5240/MAAS instead fixes this.
That's on MAAS 2.4 beta1:
root@maas01:/var/log/maas/rsyslog/vm10/2018-04-04# dpkg -l | grep maas
ii maas 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS client and command-line interface
ii maas-common 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server common files
ii maas-dhcp 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS DHCP server
ii maas-proxy 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS Caching Proxy
ii maas-rack-controller 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Rack Controller for MAAS
ii maas-region-api 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Region controller API service for MAAS
ii maas-region-controller 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Region Controller for MAAS
ii python3-django-maas 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server provisioning libraries (Python 3)
From IRC discussion:
1. /etc/maas/
2. /etc/maas/
3. /etc/maas/
4. restart maas-regiond
5. cloud-config-url was still incorrect, pointing to http://<ip>/MAAS as per the above bug.
To solve:
6. /etc/maas/