[01:31] <mup> Bug #1655798 opened: MAAS Fails to Deploy Centos 6 and 7 Images using  images.maas.io on VMs with virtio-scsi block devices <centos> <images> <MAAS:New> <https://launchpad.net/bugs/1655798>
[03:56] <rmcadams> before I rebuild a broken maas server, any point in sharing a traceback that is flooding the region log?
[04:37] <lrensing> does anyone have any tips for connection maas-region to an existing postgresql instance?
[04:38] <lrensing> i can connect manually -- via psql, but maas-region dbshell isn't allowing me to connect after changing the database host to the postgres instance
[07:38] <mup> Bug #1632480 changed: Latest Yakkety grub timesout when attempting to UEFI boot over IPv6 <maas-ipv6> <MAAS:Invalid> <grub2 (Ubuntu):Incomplete> <https://launchpad.net/bugs/1632480>
[07:38] <mup> Bug #1637570 changed: Cavium ThunderX system with 128GigB of memory is reported as having 125.9GigB of memory <arm64> <hs-arm64> <oil> <MAAS:Won't Fix> <lshw (Ubuntu):New> <https://launchpad.net/bugs/1637570>
[10:00] <mup> Bug #1627441 changed: MAAS 2.0 - CentOS 7 deployment failed <MAAS:Invalid> <maas-images:Triaged> <https://launchpad.net/bugs/1627441>
[10:00] <mup> Bug #1651156 changed: [2.1, UI] Cannot change MAAS' name from the Node listing page <MAAS:Invalid> <https://launchpad.net/bugs/1651156>
[10:00] <mup> Bug #1655798 changed: MAAS Fails to Deploy Centos 6 and 7 Images using  images.maas.io on VMs with virtio-scsi block devices <centos> <images> <MAAS:Invalid> <maas-images:Triaged> <https://launchpad.net/bugs/1655798>
[11:15] <Guest9575> Hi, I'm trying to install maas, however, I experience some problems....
[11:16] <Guest9575> I use ubuntu 16.04 LTS and maas 2.0.0~beta3+
[11:16] <Guest9575> I'm trying to run maas and regiond on one machine, just to test SW
[11:17] <Guest9575> error message I see in regiond.log is: Preparation of RegionAdvertisingService failed; will try again in 5 seconds.
[11:17] <Guest9575> then en exeption list chain ending with: django.core.exceptions.ValidationError: {'hostname': ['Nonexistant domain.']}
[11:18] <Guest9575> any idea/hint ?
[11:32] <junaidali> Guest9575: have you tried restarting regiond service
[11:32] <junaidali> ?
[11:32] <junaidali> 'maas-regiond' to be specific
[11:33] <junaidali> Is there any backup/restore feature available for MAAS like Juju?
[11:38] <Guest9575> yes, I have tried 'service maas-regiond restart' reveral times
[11:39] <Guest9575> dealing with 'Is there any backup/restore feature available for MAAS like Juju?' i'm not sure what you are asking about ;/ I've just followed documentation, doing several  'apt installs' and finished in this state
[11:56] <SimonKLB> anyone here with experience setting up openstack on maas with an external dhcp?
[11:56] <SimonKLB> the current problem im facing is that the lxd containers doesnt have their hostnames registered as dns:es anywhere
[11:56] <SimonKLB> i have openstack deployed, but im seeing NXDOMAIN exceptions on the nova-cloud-controller
[14:18] <mup> Bug #1655981 opened: removing rack controller from region controller doesn't remove it from maas db <4010> <MAAS:New> <https://launchpad.net/bugs/1655981>
[14:27] <mup> Bug #1605312 opened: Unhandled failure in updating lease. django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key" <MAAS:New> <https://launchpad.net/bugs/1605312>
[14:33] <mup> Bug #1605312 changed: Unhandled failure in updating lease. django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key" <MAAS:New> <https://launchpad.net/bugs/1605312>
[14:49] <mup> Bug #1605312 opened: Unhandled failure in updating lease. django.db.utils.IntegrityError: duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key" <MAAS:New> <https://launchpad.net/bugs/1605312>
[15:29] <Guest9575> OK, upgrading to maas 2.1.2 solved may issue, sorry for information noise :)
[15:38] <lrensing> any idea on why maas-region-api wouldn't be reading regiond.conf for the credentials to connect to postgres?
[18:40] <mup> Bug #1518226 opened: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1518226>
[18:46] <mup> Bug #1518226 changed: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1518226>
[18:52] <mup> Bug #1518226 opened: Option to add ipmipower args via webUI <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1518226>
[19:38] <rmcadams> Any ideas on connecting two kvm hosts to MAAS and having two different power providers (virsh)?
[19:41] <rmcadams> the "power address" for virsh seems to be global, which strikes me as odd
[20:07] <pmatulis> rmcadams, i think i've hit that too. well worth a bug
[20:07] <rmcadams> yah, I've tried putting them in different zones etc... still doenst work
[20:07] <rmcadams> I'm wondering if a small vm as a secondary "rack controller" will fix it
[20:07] <rmcadams> but I'll file a bug, to me that should be a per "server" setting
[20:11] <pmatulis> it should be a per-node setting
[20:12] <rmcadams> yah, thats what I meant by "server" sorry
[20:14] <pmatulis> ah ok
[20:19] <rmcadams> bug filed, we'll see what they say
[20:19] <mup> Bug #1656091 opened: Power Settings for virsh are not per node, they are global <MAAS:New> <https://launchpad.net/bugs/1656091>
[20:26] <rmcadams> pmatulis: you think a second rack controller might fix it?
[20:26] <rmcadams> well, work around I guess.
[20:26] <pmatulis> rmcadams, probably but it would be a shame to go there
[20:27] <rmcadams> agreed, it's for a lab environment so it's not a bad idea for the team to test running multiple rack controllers etc..
[20:27] <rmcadams> so for a work around it might work to get them going :)
[20:28] <pmatulis> rmcadams, actually a 2nd rackd would just allow HA on rackd services. i don't think it would help
[20:29] <rmcadams> ahh ok
[20:29] <pmatulis> you would still be connecting to the regiond instance, which provides the API and web UI
[20:31] <rmcadams> right
[20:41] <rmcadams> oh hey, pmatulis  works for Canonical, how ironic.
[20:42] <pmatulis> rmcadams, hm?
[20:43] <rmcadams> I just got a laugh because here I am chatting away bout this and I didnt realize you were tagged on that bug/worked for canonical, sorry :)
[20:55] <jtilander> During deployment of Ubuntu I get stuck on a GRUB load screen, with one entry "Local"
[20:56] <jtilander> This is for an IBM server, I can deploy fine to my local WMware VM and a physical Dell laptop. Seems very strange. Any ideas?