I'm trying to build a MaaS cluster and this is what I've done so far:
Region Controller
- install ubuntu 14.10
- configure interfaces
- configure dns
apt update
apt upgrade
apt install maas-region-controller
dpkg-reconfigure maas-region-controller
—-> http://192.168.10.1/MAAS/- create new root account
- login
Cluster Controller
- install ubuntu 14.10
- configure interfaces
- configure dns
apt update
apt upgrade
apt install maas-cluster-controller
dpkg-reconfigure maas-cluster-controller
—-> 192.168.10.1maas login <maas_user> http://192.168.10.1/MAAS/ <api_key>
Check MaaS web interface… no clusters appear in the clusters tab. Just to confirm they are on the same network. regardless I can log into maas from the cluster controller… but it doesn't seem to make a difference in the outcome.
I've been troubleshooting this for 4 days now and its getting rough…. does anyone know what makes these two communicate properly?
Best Answer
The first clue to the answer lies in the log /var/log/maas/pserv.log on the cluster-controller. The problem was essentially an authentication failure.
The second clue came from the region-controller's /var/log/maas/apache2/error.log.
For those that are curious I changed up my IP scheme to my eth0 interfaces which is the cause for the disparity but that did not fix anything.
This is likely a bug as in general this should happen... however the node should still show up in MaaS as pending waiting for administrator approval.
Once approval is given (from my understanding of how the system should work) the
/var/lib/maas/secret
password is transmitted from the region-controller to the cluster-controller.Unfortunately the server never hits the pending state so this may not be performed. Therefore what must be done to resolve this issue is to transfer your secret manually through the following commands:
Region Controller
Copy the output it should be a ~16 digit hex code. Then on your cluster controller run the following command and enter your copied "secret".
Cluster Controller
lastly connect to the server through an API query of your choice (this probably isn't necessary but it does force the connection).