=== zz_CyberJacob is now known as CyberJacob
=== CyberJacob is now known as zz_CyberJacob
=== TheRealMue is now known as TheMue
=== amaged__ is now known as amaged_
=== wolverineav_ is now known as wolverineav
=== zz_CyberJacob is now known as CyberJacob
=== CyberJacob is now known as zz_CyberJacob
=== zz_CyberJacob is now known as CyberJacob
=== CyberJacob is now known as zz_CyberJacob
=== zz_CyberJacob is now known as CyberJacob
=== menn0_ is now known as menn0
=== rozie_ is now known as rozie
[18:01] <bhundven> having a problem adding my initial node to maas. I have the api url set to 172.16.0.52, and the internal interface of the cluster is 192.168.254.x/24. During the commission of the initial node, I see it trying to connect to http://172.16.0.55/... and failing. I believe this is due to the nat setup.
[18:04] <roaksoax> bhundven: the nodes under MAAS should be able to access the region controller
[18:05] <roaksoax> bhundven: so, dpkg-reconfigure maas-cluster-controller , and make it point to the address in the 192.168.254.x/24 range
[18:05] <bhundven> right, but then I won't be able to access maas from the 172. side of the network.
[18:09] <roaksoax> bhundven: you can
[18:09] <roaksoax> bhundven: the region (webapp) listens in *all* networks
[18:10] <bhundven> ah, ok!
[18:10] <bhundven> roaksoax: thanks!
[18:10] <bhundven> I shoulda checked netstat :P
[20:36] <bhundven> roaksoax: ok. Sorry for my ignorance, but I'm learning fast here. I'm deploying the first node still, I've tried different ubuntu versions, but see the same thing in the cloud-init: /var/lib/cloud/instance/scripts/user_data.sh: 18: /var/lib/cloud/instance/scripts/user_data.sh: initctl: not found
[20:36] <bhundven> then it says its powering off