[02:39] <mup> Bug #1741179 opened: package maas-region-api 2.2.0+bzr6054-0ubuntu2~16.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 <amd64> <apport-package> <need-duplicate-check> <yakkety> <maas (Ubuntu):New> <https://launchpad.net/bugs/1741179>
[04:24] <mup> Bug #1731293 changed: [2.3rc2, UI] Previous results should be sorted by most recent first <2.3qa> <ui> <MAAS:Expired> <https://launchpad.net/bugs/1731293>
[04:33] <mup> Bug #1731293 opened: [2.3rc2, UI] Previous results should be sorted by most recent first <2.3qa> <ui> <MAAS:Expired> <https://launchpad.net/bugs/1731293>
[04:39] <mup> Bug #1731293 changed: [2.3rc2, UI] Previous results should be sorted by most recent first <2.3qa> <ui> <MAAS:Expired> <https://launchpad.net/bugs/1731293>
[12:15] <mup> Bug #1712680 changed: cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS. <cloud-init:Fix Committed> <MAAS:Invalid> <maas-images:New for ltrager> <https://launchpad.net/bugs/1712680>
[13:21] <mup> Bug #1743776 opened: [2.3, 2.4] Editing a custom repository doesn't allow you to modify distribution, component. <MAAS:New> <https://launchpad.net/bugs/1743776>
[13:52] <mup> Bug #1736626 changed: [2.4] Cannot add device from dashboard <MAAS:Invalid> <https://launchpad.net/bugs/1736626>
[14:34] <mup> Bug #1743776 changed: [UI, 2.3] Editing a custom repository doesn't allow you to modify distribution, component. <MAAS:Invalid by ack> <MAAS 2.3:Triaged by ack> <https://launchpad.net/bugs/1743776>
[14:40] <ejsf> hi, just installed maas and commissioned my first nodes, im impressed, very nice product :) just one question, i added the first node by hand and now i want to rename it, is there a way to rename a machine or is it better to delete it and add again?
[15:08] <ejsf> deleting and re-adding worked :)
[20:07] <mup> Bug #1679322 opened: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1679322>
[20:13] <mup> Bug #1679322 changed: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1679322>
[20:16] <mup> Bug #1679322 opened: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server <maas (Ubuntu):Incomplete> <https://launchpad.net/bugs/1679322>
[21:31] <desigabri> hi
[21:31] <desigabri> please just a little help
[21:32] <desigabri> I read about Maas and I undertood that just the first machine need the ubuntu server plus maas...
[21:33] <desigabri> the other machines have just to be connected in PXE boot
[21:34] <desigabri> so I'll configure those machine from the primary node?
[21:34] <desigabri> is it right?
[21:35] <desigabri> so just more hardware power connecting and then bigger machine?
[21:37] <desigabri> is it a way to upgrade hardware power just connecting more hardware?
[21:37] <desigabri> connecting togheter
[21:52] <gunix> how do i assing a subnet to a space?
[21:52] <gunix> there is no button
[21:54] <gunix> also how can i enable dhcp?
[22:06] <gunix> found dhcp somewhere
[22:06] <gunix> pxe doesn't work unless maas is the dhcp server, it seems
[22:09] <gunix> i managed to get the vm to boot from maas, with the default image, but after that it rebooted and got stuck cause it doesn't find any bootable device
[22:33] <gunix> the error i get is "failed to enlist system maas server"
[23:04] <gunix> i figure this is where it is failing: https://github.com/cloudbase/maas/blob/master/contrib/preseeds_v2/enlist_userdata#L100-L130
[23:04] <gunix> as i get exactly that echo
[23:04] <gunix> on the screen
[23:07] <gunix> found an IP that shouldn't be there. there was a bad entry in /etc/hosts on the maas controller
[23:18] <gunix> ok, found the old IP in maas and bind9 settings files. changed that. rebooted once, machine popped in dashboard, rebooted again to scan hardware
[23:32] <gunix> i have progress. now the error i get is that mass can't detect storage, which is a virtio device on qemu
[23:38] <gunix> yep, hardware tests fail
[23:58] <gunix> fixed with hwe kernel. i THINK that is what solved the issue