[00:57] <jac_cplane> I'm running into bug 1628337 - cloud init install NTP before configuring archives.   I see from github that it was fixed 20 days ago.  can someone tell me how I can get this fix?   i'm running MAAS 2.1.5 - I deleted my current xenial image and downloaded it again via maas.
[00:57] <jac_cplane> which didn't fix it
[00:58] <jac_cplane> do I need to edit MAAS config ?
[00:58] <jac_cplane> I also did a apt-get update on my maas server
[00:59] <jac_cplane> trusty deploys fine but xenial fails
[01:04] <jac_cplane> Do I need to edit cloudinit in maas server /usr/lib/python3/dist-packages/cloudinit/config/cc_ntp.py and patch myself?
[01:18] <jac_cplane> please disregard.  figured it out.
[01:22] <roaksoax> jac_cplane: what was it ?
[01:22] <jac_cplane> apt-get update followed by apt-get upgrade
[01:23] <jac_cplane> coming from rh/centos  yum update does both.
[07:37] <mup> Bug #1731405 opened: disk names in gui don't transfer through to node device names <MAAS:New> <https://launchpad.net/bugs/1731405>
[14:23] <mup> Bug # changed: 1662343, 1721825, 1722646, 1723425, 1728304, 1730474, 1730481, 1730485, 1730703, 1730799, 1731075, 1731292, 1731350
[14:53] <mup> Bug #1721743 changed: [2.3b2] Rack and region controller versions still not updated <MAAS:Fix Released> <https://launchpad.net/bugs/1721743>
[14:53] <mup> Bug #1731490 opened: Can't boot MAAS with a UEFI Node and a Ubuntu custom storage layout <MAAS:New> <https://launchpad.net/bugs/1731490>
[16:03] <jamesbenson> roaksoax: ping
[21:23] <mup> Bug #1618466 changed: [2.1] Fail to add PPA behind maas-proxy <MAAS:Triaged> <https://launchpad.net/bugs/1618466>
[21:38] <pzingg> Newbie, working my way through first deployment. Got node through commissioning but getting "No filesystems." and "No available disks or partitions."
[21:39] <pzingg> I can see the disk in the "07-block-devices" output. Is it because I already have Ubuntu installed on these disks/partitions?
[21:40] <pzingg> Can't find any documentation on this.
[23:07] <shadoxx_> pzingg: more than likely, yes, that's why it's failing
[23:07] <shadoxx_> ideally the node you have will have blank disks when commissioning and deployed
[23:23] <pzingg> I'm going to see if there's a way to either release a yet-to-be-deployed node, or command line into it to run gparted and blow away the partitions.
[23:23] <shadoxx_> pzingg: generally i just used gparted or do something fun like dd if=/dev/zero of=/dev/drive bs=512 count=8