[08:52] <freeflyi1g> hi, normally, maas adds a CNAME record into bind's zone file after a machine been allocated, right?
[08:53] <bigjools> it adds it when it knows its IP
[08:53] <bigjools> which depends on the leases scanner working correctly
[08:56] <freeflyi1g> my problem is only the machine used for juju bootstrap has its CNAME added, and not the rest of instances, so I can't reach them by using domain name
[08:57] <freeflyi1g> is this normal or a bug?
[09:00] <bigjools> could be neither :)
[09:00] <bigjools> are the instances deployed correctly?
[09:01] <bigjools> well, you should see CNAMEs once they finish commissioning
[09:01] <bigjools> which maas version?
[09:01] <freeflyi1g> bigjools: yes, some have been deployed correctly, when I try to add-relation between them, failed, due to the domain name couldn't be resolved
[09:01] <bigjools> did you check the zone file to see if it was added?
[09:02] <bigjools> no reason they won't get added if the bootstrap node had its one added
[09:02] <freeflyi1g> bigjools: the one in saucy, plus a fix from bzr for empty filename
[09:02] <bigjools> ok
[09:02] <freeflyi1g> bigjools: I checked the zone file, only on has been added, not any others
[09:02] <bigjools> you can use the daily builds PPA for that if you want
[09:03] <bigjools> can you check that their DHCP leases are in the database
[09:04] <freeflyi1g> bigjools: http://paste.ubuntu.com/5932076/
[09:05] <freeflyi1g> bigjools: the last line was added manually, and also some entries at the begining of the file
[09:06] <bigjools> freeflyi1g: do you know how to use "maas shell" to examine what's in DHCPLease?
[09:07] <freeflyi1g> bigjools: sorry, no
[09:07] <bigjools> ok hang on I'm in the middle of something, I'll help you shortly
[09:07] <bigjools> unless someone beats me to it
[09:09] <freeflyi1g> bigjools: no worries, take your time
[09:10] <bigjools> if you know Django you can use Python in maas shell
[09:13] <freeflyi1g> bigjools: which module shall I use to check it
[19:19] <AskUbuntu> Maas VMs stopped at maas-enlisting-node login? | http://askubuntu.com/q/327114
[20:08] <burnbrighter> Hi - Is MAAS still being actively developed?
[22:24] <bigjools> burnbrighter_: yes
[22:25] <bigjools> freeflying: sorry I didn't get to you yesterday
[23:31] <burnbrighter_> Thanks bigjools
[23:32] <bigjools> welcome
[23:39] <burnbrighter_> bigjools: I'm working with wmware fusion to experiment with running maas in virt environment.  I saw guides posted by security team.  I believe them to be outdated.  I am running my nodes to be enlisted on PXE boot with maas-dhcp on my controller node on vmnet3 network with 172.16.118.x network.  How do I force the controller node to offer maas-dhcp (and dns) services on my vmnet3 adapter on the 172.16.118.x network?  The contoll
[23:39] <burnbrighter_> on my regular network via 192.168.1.x
[23:40] <burnbrighter_> it seems cobbler is no longer used. which is good.  We talked about that a long time ago.
[23:40] <bigjools> burnbrighter_: there's configuration for different networks in the UI, you have to set each one up
[23:40] <burnbrighter_> it has been some time since I've worked with maas
[23:41] <burnbrighter_> I'll look
[23:41] <bigjools> go into the cluster config
[23:42] <burnbrighter_> Now I've done some LOL - 500 internal server erro
[23:42] <bigjools> oops