[04:21] <mup> Bug #1472260 changed: MAAS picks wrong cluster-controller for curtin install <MAAS:Expired> <https://launchpad.net/bugs/1472260>
[04:21] <mup> Bug #1474792 changed: maas installation bughit <MAAS:Expired> <https://launchpad.net/bugs/1474792>
[04:24] <mup> Bug #1472260 opened: MAAS picks wrong cluster-controller for curtin install <MAAS:Expired> <https://launchpad.net/bugs/1472260>
[04:24] <mup> Bug #1474792 opened: maas installation bughit <MAAS:Expired> <https://launchpad.net/bugs/1474792>
[04:27] <mup> Bug #1472260 changed: MAAS picks wrong cluster-controller for curtin install <MAAS:Expired> <https://launchpad.net/bugs/1472260>
[04:27] <mup> Bug #1474792 changed: maas installation bughit <MAAS:Expired> <https://launchpad.net/bugs/1474792>
[04:30] <thetrav> I've got a new maas deployment on a system with 2 NICs.  eth0 is where I want to connect to the web interface, eth1 is where the managed hosts will be asking for their DHCP.  Trick is, the managed hosts won't be able to route to eth0
[04:31] <thetrav> right now i'm having trouble where the hosts aren't able to pull metadata
[04:34] <thetrav> http://askubuntu.com/questions/641454/maas-virtualbox-calling-http-169-254-169-254-2009-04-04-meta-data-instance-id <- basically it's that guy's problem
[04:34] <thetrav> my suspicion is that maas is getting an ARP saying "who has 169.254.169.254" and is replying with the mac of eth0
[04:36] <mup> Bug #1472260 opened: MAAS picks wrong cluster-controller for curtin install <MAAS:Expired> <https://launchpad.net/bugs/1472260>
[04:36] <mup> Bug #1474792 opened: maas installation bughit <MAAS:Expired> <https://launchpad.net/bugs/1474792>
[04:38] <thetrav> actually tcpdump shows me that the node has an iscsi device from the maas host anyway, so why is it even using http cloud-init rather than config-drive?
[04:39] <mup> Bug #1472260 changed: MAAS picks wrong cluster-controller for curtin install <MAAS:Expired> <https://launchpad.net/bugs/1472260>
[04:39] <mup> Bug #1474792 changed: maas installation bughit <MAAS:Expired> <https://launchpad.net/bugs/1474792>
[09:16] <mup> Bug #1446525 changed: Curt tries to umount /tmp filesystem while commands are running. <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1446525>
[09:25] <mup> Bug #1471731 changed: McDivitt console not available after deployment <MAAS:Invalid> <https://launchpad.net/bugs/1471731>
[09:25] <mup> Bug #1507434 changed: Commissioning multiple VM's with Virsh power type results on vm's never powered on <MAAS:Invalid> <https://launchpad.net/bugs/1507434>
[09:28] <mup> Bug #1471731 opened: McDivitt console not available after deployment <MAAS:Invalid> <https://launchpad.net/bugs/1471731>
[09:28] <mup> Bug #1507434 opened: Commissioning multiple VM's with Virsh power type results on vm's never powered on <MAAS:Invalid> <https://launchpad.net/bugs/1507434>
[09:31] <mup> Bug #1471731 changed: McDivitt console not available after deployment <MAAS:Invalid> <https://launchpad.net/bugs/1471731>
[09:31] <mup> Bug #1507434 changed: Commissioning multiple VM's with Virsh power type results on vm's never powered on <MAAS:Invalid> <https://launchpad.net/bugs/1507434>
[09:34] <mup> Bug #1471731 opened: McDivitt console not available after deployment <MAAS:Invalid> <https://launchpad.net/bugs/1471731>
[09:34] <mup> Bug #1507434 opened: Commissioning multiple VM's with Virsh power type results on vm's never powered on <MAAS:Invalid> <https://launchpad.net/bugs/1507434>
[09:46] <mup> Bug #1471731 changed: McDivitt console not available after deployment <MAAS:Invalid> <https://launchpad.net/bugs/1471731>
[09:46] <mup> Bug #1507434 changed: Commissioning multiple VM's with Virsh power type results on vm's never powered on <MAAS:Invalid> <https://launchpad.net/bugs/1507434>
[09:55] <mup> Bug # changed: 1467341, 1473069, 1481276, 1501135, 1505613
[10:07] <mup> Bug #1501135 changed: maas-import-pxe-files fails when MAAS_URL is quoted <MAAS:Invalid> <maas (Ubuntu):Invalid> <maas (Ubuntu Trusty):Invalid> <https://launchpad.net/bugs/1501135>
[10:10] <liviaandcarla> testing
[11:01] <mup> Bug #1515188 opened: [1.9] VmWare power management doesn't work with vm name <MAAS:New> <https://launchpad.net/bugs/1515188>
[11:01] <mup> Bug #1515191 opened: Welcome screen login button design is secondary instead of primary <ui> <MAAS:Triaged> <https://launchpad.net/bugs/1515191>
[11:34] <mup> Bug #1515203 opened: MAAS UI has no report a bug link <ui> <MAAS:New> <https://launchpad.net/bugs/1515203>
[14:47] <mup> Bug #1515275 opened: Error creating a bond <MAAS:New for andreserl> <https://launchpad.net/bugs/1515275>
[14:47] <mup> Bug #1515276 opened: Error creating a bond <MAAS:New for andreserl> <https://launchpad.net/bugs/1515276>
[20:09] <mup> Bug #1515380 opened: [1.9rc1] Network bonds management unresponsive in UI <MAAS:New> <https://launchpad.net/bugs/1515380>
=== mup_ is now known as mup