[01:14] <bigjools> mattrae: that usually indicates a dhcp leases parsing problem
[02:29] <mattrae> bigjools: thx, yeah i was seeing the leases file still show the hostname as maas-enlist for hosts that were deployed.. unless i was confused
[02:29] <bigjools> the leases file doesn't have hostnames, what do you mean?
[02:30] <mattrae> bigjools, roaksoax here's some of the different errors i've received. i think i saw a validation error regarding a mac address as well. http://pastebin.com/WKcBv9zt
[02:31] <bigjools> mattrae: that paste means nothing to me, I need to see actual logs
[02:33] <mattrae> bigjools: those are the exceptions raised. i had to write them down. i'll see if i can get better logs
[02:38] <mattrae> bigjools: regarding the hostname in the leases file, its 'client-hostname'. looks like thats sent by the client.. i'm just trying to find other symptoms that could possibly be related to why some nodes are not being added to the zone file. thats my main issue, and
[02:38] <bigjools> mattrae: the primary reason in my experience is that there's something funky in the leases file that prevents maas from parsing it
[02:38] <bigjools> the DNS entries are all driven from there
[02:39] <bigjools> so first check that your expected IP/MAC is in there and then check the logs
[02:39] <bigjools> the leases file format is fragile :/
[02:39] <mattrae> ah sweet, so if i'm able to fix the leases file that may fix the zone file?
[02:39] <bigjools> no, it might be a parsing bug
[02:40] <mattrae> cool well that gives me some hints.. i'll look at the leases file
[02:40] <bigjools> or it could just be that the leases file is not getting parsed at all
[02:43] <mattrae> ahh ok, i'll keep that in mind when i look at it again tomorrow
[02:50] <bigjools> make sure that the celery log shows the job running
[13:07] <AskUbuntu> How to delete a MaaS node which is in 'commissioning' state? | http://askubuntu.com/q/266924
[13:17] <mattrae> roaksoax: i'll try to get more logs from maas/libvirt/syslog today. right now we're working around the dns issue by manually editing the zone file to add records it forgot to add. if i can continue doing that I will to get the rest of the nodes deployed.
[13:18] <mattrae> roaksoax: we were running into additional problems deploying to nodes though, juju could not find machines that were 'Ready'. I tried different constraints and removing constraints. it could have been a typo so we're trying to add those nodes again today
[14:30] <roaksoax> mattrae: ok remember to clearout constraints as they seem to be permanent
[14:30] <roaksoax> or "global"
[14:34] <mgz> `juju set-constraints arch= cpu= mem=` should be enough if you're reusing a bootstrapped environment but don't have any services
[14:34] <mgz> ah, sorry, =any, not =
[14:35] <roaksoax> mattrae: ^^
[14:37] <mgz> generally you want to do `juju destroy-environment` if you've made maas config changes, which will blow away most juju settings except those you have locally in ~/.juju/environments.yaml
[14:50] <mattrae> roaksoax, mgz: sweet that will help. i'll make sure there are no constraints
[14:50] <mattrae> roaksoax: right now we are enlisting a node and getting an exception of "one or more MAC addresses is invalid". I have a printout of the exception and the lease
[14:51] <mattrae> roaksoax: the maas interface shows that the node is declared. is this exception something to worry about?
[14:52] <roaksoax> uhmm if it got enlisted dont think so
[14:52] <mattrae> cool sounds good
[16:59] <mattrae> roaksoax, bigjools: i am leaning strongly on the issue of nodes not getting added to dns being related to the leases file. i see that the leases file has different info for nodes that are added to dns and nodes that aren't. i'll work on getting the leases file to examine
[17:00] <roaksoax> mattrae: that might be related to an issue in isc-dhcp
[17:00] <mattrae> there is a private lp bug opened to track the issue https://bugs.launchpad.net/ubuntu-advantage/+bug/1154184
[23:04] <bigjools> roaksoax: hey
[23:04] <bigjools> when is the sru planned?