[00:06] <mup> Bug #1443700 was opened: Node.release is not using post_commit hooks <MAAS:Triaged> <https://launchpad.net/bugs/1443700>
[00:25] <mup> Bug #1443709 was opened: Error on request (58) node.check_power <MAAS:Triaged> <https://launchpad.net/bugs/1443709>
[09:35] <mup> Bug #1441471 changed: MAAS python-vmomi power type: can't "add chassis" twice <MAAS:Invalid by mpontillo> <https://launchpad.net/bugs/1441471>
[09:35] <mup> Bug #1443840 was opened: Paper background image loaded from assets.ubuntu.com not locally <MAAS:New> <https://launchpad.net/bugs/1443840>
[09:47] <mup> Bug #1441471 was opened: MAAS python-vmomi power type: can't "add chassis" twice <MAAS:Invalid by mpontillo> <https://launchpad.net/bugs/1441471>
[09:47] <mup> Bug #1443840 changed: Paper background image loaded from assets.ubuntu.com not locally <MAAS:New> <https://launchpad.net/bugs/1443840>
[09:53] <mup> Bug #1441471 changed: MAAS python-vmomi power type: can't "add chassis" twice <MAAS:Invalid by mpontillo> <https://launchpad.net/bugs/1441471>
[09:53] <mup> Bug #1443840 was opened: Paper background image loaded from assets.ubuntu.com not locally <MAAS:New> <https://launchpad.net/bugs/1443840>
[12:23] <mup> Bug #1443917 was opened: IntegrityError: duplicate key value violates unique constraint "maasserver_componenterror_component_key", (component)=(clusters) already exists <MAAS:New> <https://launchpad.net/bugs/1443917>
[13:35] <mup> Bug #1443958 was opened: 1.8beta2: Can't double/triple click to select word/all in power parameters text boxes <oil> <MAAS:New> <https://launchpad.net/bugs/1443958>
[13:35] <mup> Bug #1443959 was opened: 1.8beta2: Going back from node page to node listing page loses filter <oil> <MAAS:New> <https://launchpad.net/bugs/1443959>
[15:06] <mup> Bug #1443986 was opened: 	crochet._eventloop.TimeoutError:  <MAAS:New> <https://launchpad.net/bugs/1443986>
[15:18] <mup> Bug #1444012 was opened: 1.8beta2: settings page rendering is all messed up <oil> <MAAS:Confirmed> <https://launchpad.net/bugs/1444012>
[15:30] <mup> Bug #1444012 changed: 1.8beta2: settings page rendering is all messed up <oil> <MAAS:Confirmed> <https://launchpad.net/bugs/1444012>
[15:36] <mup> Bug #1444012 was opened: 1.8beta2: settings page rendering is all messed up <oil> <MAAS:Confirmed> <https://launchpad.net/bugs/1444012>
[15:36] <mup> Bug #1444018 was opened: 1.8beta2: can't tell which stream my images came from after changing streams <oil> <MAAS:New> <https://launchpad.net/bugs/1444018>
[16:06] <AskUbuntu> Juju - Proxy issue | http://askubuntu.com/q/609240
[16:06] <mup> Bug #1444039 was opened: 1.8beta2: View release notes and view documentation links broken <oil> <MAAS:New> <https://launchpad.net/bugs/1444039>
[16:09] <mup> Bug #1444039 changed: 1.8beta2: View release notes and view documentation links broken <oil> <MAAS:New> <https://launchpad.net/bugs/1444039>
[16:21] <mup> Bug #1444039 was opened: 1.8beta2: View release notes and view documentation links broken <oil> <MAAS:New> <https://launchpad.net/bugs/1444039>
[18:38] <j^2> ping
[18:38] <j^2> anyone around?
[18:40] <bmorriso> Is this chat logged somewhere?
[18:41] <bmorriso> I asked a question last night and I'm curious if it was answered. Hate to ask it again.
[18:41] <j^2> yeah
[18:41] <j^2> i’m not sure
[18:46] <bmorriso> I have a host that is failing to deploy. It comes up on the terminal, but it never pushes keys. Where might logs exist to try and determine why it is failing? It seems it is impossible to get the password set for the ubuntu user to log in on the console.
[19:14] <bmorriso> Using the debian installer and a custom preseed, I was under the impression that it over wrote what existed the more specific preseed? Is this not the case? base (all the settings) trusty (trusty specific settings) host (host specific settings). The behavior I saw last week was that it doesn't inherit -- but rather expects a full-blow preseed for host-specific configuration.
[19:20] <ctlaugh> I am looking for some DNS-related help... I had a working MAAS/Juju deployment that I just had to move from one lab/network to another.  Now, the nodes I have deployed using Juju can no longer resolve DNS.  The system running the MAAS controller is working fine.  If I modify resolv.conf and manually add the DNS server (instead of the entry for the MAAS server), the node works fine as well.
[19:22] <ctlaugh> ^^ Something seems to not be right with DNS forwarding
[19:24] <j^2> i just posted this: http://jjasghar.github.io/blog/2015/04/14/maas-setting-up-region-controller-and-cluster-controller/
[19:25] <j^2> it seems to be lacking in the documentation
[19:39] <ctlaugh> I think I just found the problem -- I went to using a gateway running dnsmasq (trusty) and I was getting a lot of DNSSEC-related errors (http://askubuntu.com/questions/537540/ubuntu-maas-dns-not-forwarding-request).  And, I just found that dnsmasq in trusty does not seem to support DNSSEC (https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1363366).  So, once I disabled DNSSEC in bind on the MAAS
[19:39] <ctlaugh> controller, DNS forwarding is working.
[19:46] <bmorriso> IRC logs for those that might want to know http://irclogs.ubuntu.com/
[21:33] <mup> Bug #1444154 was opened: UX: Adding a VMware (python-pyvmomi) node should not require a VM UUID <MAAS:In Progress by mpontillo> <https://launchpad.net/bugs/1444154>
[22:20] <bmorriso> Anyone around well versed with Curtin???