[04:09] <mup> Bug #1578908 opened:  [2.0b4] Unable to run MAAS in an unprivileged LXC container <MAAS:New> <https://launchpad.net/bugs/1578908>
[05:03] <mup> Bug #1577890 changed: [2.0b3] UEFI PXE boot fails on Intel NUK - NBP filesize is 0 Bytes PXE-E99: Unexpected network error. (OrangeBox) <MAAS:Invalid> <https://launchpad.net/bugs/1577890>
[06:36] <mup> Bug #1578908 changed:  [2.0b4] Unable to run MAAS in an unprivileged LXC container <MAAS:Opinion> <https://launchpad.net/bugs/1578908>
[08:12] <janef> Hi friends,
[08:13] <janef> I am getting following error while doing the pxe boot
[08:13] <janef> url_helper.py[WARNING]: Calling 'http://169.254.168.254/2009-04-04/meta-data/instance-id failed [x/y]:  url error [[Errno 113] No route to host]
[08:14] <janef> do anybody have idea regarding this
[08:16] <DavidRama> guessing that your DHCP server didn't provide a valide IP
[08:17] <janef> ok
[08:25] <janef> yes it is
[08:26] <janef> It was the configuration issue problem
[08:26] <janef> sudo dpkg-reconfigure maas-cluster-controller this solved the issue
[08:28] <janef> oh no
[08:28] <janef> Its not working :(
[08:29] <DavidRama> did you delcare the PXE Lan as DHCP managed in your maas ?
[08:30] <janef> yes
[08:31] <DavidRama> your maas is directly connected to the PXE LAN ?
[08:32] <DavidRama> no routing ?
[08:32] <janef> I have two interfaces
[08:32] <janef> eth0 and 1
[08:32] <janef> eth1 is DHCP
[08:33] <DavidRama> did you check that the if are not "swappped" ?
[08:33] <DavidRama> ie eth0 is doing the DHCP instead of eth1
[08:36] <janef> How to check that "swapping"
[13:29] <mup> Bug #1579073 opened: [ERROR] Failed to probe and enlist VMware nodes: 'vim.Folder' object has no attribute 'summary' <MAAS:New> <https://launchpad.net/bugs/1579073>
[14:45] <plars> Hi, I'm trying to deploy a xenial unit on maas with juju, I checked xenial to import last week, and on the maas UI it looks like it's available. But when I try to do it, I get this:
[14:45] <plars> https://www.irccloud.com/pastebin/DDUhkBwX/
[14:46] <plars> any way to confirm what's missing with xenial? on the web ui it seems to think it's there
[14:54] <plars> It looks kind of similar to https://bugs.launchpad.net/maas/+bug/1419041
[15:00] <brendand> i recently hit similar
[15:01] <brendand> plars, did you upgrade maas recently?
[15:02] <plars> brendand: nope
[15:02] <plars> brendand: we are currently on 1.8.0+bzr4001-0ubuntu2~trusty1 from the stable ppa (previously recommended to work around other issues which I can't recall right now)
[15:03] <plars> brendand: there's updates available, but I'm not sure I want to just update in hopes that it might solve something, or might break other things
[15:03] <brendand> plars, i think the thing i saw was caused by updating actually
[15:03] <brendand> so definitely wasn't suggesting that as a fix
[15:04] <plars> yeah :)
[15:07] <brendand> plars, do you have api/cli access?
[15:07] <plars> brendand: yes
[15:08] <brendand> can you try boot-resources read? maybe you've done that already
[15:08] <plars> brendand: yes, it shows up there:
[15:08] <plars> https://www.irccloud.com/pastebin/NFuPTeAt/
[15:09] <brendand> where is that error shown btw?
[15:10] <plars> brendand: I see it in juju status
[15:11] <brendand> plars, maybe i'm misreading it but it's sending xenial, but it's in boot-resources as ubuntu/xenial
[15:11] <brendand> maybe that doesn't matter
[15:12] <brendand> also odd that xenial isn't in the list 'it should be one of'
[15:12] <brendand> probably something to ask juju folks as well
[15:12] <plars> brendand: the trusty one is ubuntu/trusty, I don't think it should matter
[15:13] <plars> brendand: do you know if there's another place it checks for the list of available distro_series?
[15:14] <plars> brendand: I started here, because the agent error referenced a 400 received back from gomaasapi
[15:17] <brendand> plars, would be good to know what api call juju is making, i can't figure it out from the paste
[15:39] <brendand> as for my problems, pxe booting my kvm nodes seems to have stopped working on 2.0
[16:50] <mup> Bug #1579150 opened: MAAS 1.8 - can't provision nodes <MAAS:New> <https://launchpad.net/bugs/1579150>
[17:20] <mup> Bug #1579159 opened: tag popluation should be done in a post-commit hook <MAAS:New> <https://launchpad.net/bugs/1579159>
[17:26] <mup> Bug #1579159 changed: tag popluation should be done in a post-commit hook <MAAS:New> <https://launchpad.net/bugs/1579159>
[17:35] <mup> Bug #1579159 opened: tag popluation should be done in a post-commit hook <MAAS:New> <https://launchpad.net/bugs/1579159>
[19:19] <bdx> hey whats up guys? Are you aware of the 'RegionAdvertisingService' object has no attribute 'processId' in beta5?
[19:25] <bdx> https://bugs.launchpad.net/maas/+bug/1579199
[19:51] <mup> Bug #1579199 opened: 'RegionAdvertisingService' object has no attribute 'processId' in beta5 <MAAS:New> <https://launchpad.net/bugs/1579199>
[20:12] <mup> Bug #1579215 opened: [2.0b4] Can attempt to commission enlisted nodes without chosen power type <MAAS:New> <https://launchpad.net/bugs/1579215>
[20:34] <bdx> hey whats up everyone? Is there anything I can do to get beta5 to work?
[20:42] <mup> Bug #1579199 changed: 'RegionAdvertisingService' object has no attribute 'processId' in beta5 <MAAS:New> <https://launchpad.net/bugs/1579199>
[21:33] <mup> Bug #1579238 opened: Deploying a custom image seems to be broken with Xenial for commissioning/deployment <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1579238>
[21:45] <mup> Bug #1579238 changed: Deploying a custom image seems to be broken with Xenial for commissioning/deployment <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1579238>
[21:48] <mup> Bug #1579238 opened: Deploying a custom image seems to be broken with Xenial for commissioning/deployment <hwcert-server> <MAAS:New> <https://launchpad.net/bugs/1579238>
[23:17] <plars> brendand: so this looks a lot like the bug I'm hitting: https://bugs.launchpad.net/maas/+bug/1537095
[23:31] <mup> Bug #1579238 changed: Deploying a custom image seems to be broken with Xenial for commissioning/deployment <hwcert-server> <MAAS:Invalid> <https://launchpad.net/bugs/1579238>