[10:11] <mup> Bug #1604339 opened: Node names are hidden in nodes listing <ui> <MAAS:New> <https://launchpad.net/bugs/1604339>
[11:57] <mup> Bug #1604375 opened: The action panel needs indenting from the edge of the screen <ui> <ux> <MAAS:New> <https://launchpad.net/bugs/1604375>
[12:10] <ram_> Hi. I installed MAAS on one server. I have taken another two servers in which have the boot type as PXE. MAAS detected nodes. while doing commissioning it was failing. Could you please help me in this
[12:15] <ram_> I saw some log files under /var/log/maas/ . http://paste.openstack.org/show/537405/
[12:16] <ram_> http://paste.openstack.org/show/537405/ has log files output. could you guys please help me in solving this issue.
[12:59] <roaksoax> ram_: /win 11
[13:00] <roaksoax> ram_: what version fo MAAs are you using ?
[13:03] <mup> Bug #1604393 opened: MAAS is not listing the storage disks <MAAS:New> <https://launchpad.net/bugs/1604393>
[13:04] <ram_> roaksoax: Hi. I am using  MAAS Version 1.9.3+bzr4577-0ubuntu1 (wily1)
[13:06] <roaksoax> ram_: you need to provide cloud-init logs. When you comission, click on the option to prevent power off, and ssh into the machine while commissioning
[13:06] <roaksoax> ram_: and grab /var/log/cloud-init*
[13:07] <ram_> roaksoax: OK. Thank you. I will try that now.
[13:18] <acovrig> How do I tie a controller to a VLAN? the default untagged on fabric-0 is attached just fine, but when I add a VLAN for DHCP it doesn’t let me add my controller as the rack controller when configuring DHCP
[13:28] <roaksoax> acovrig: i dont quite understand what you are trying to do fully ?
[13:28] <roaksoax> acovrig: you want to add a second rack controller ?
[13:33] <acovrig> no, add a second network to my existing controller
[13:35] <acovrig> so I have an interface for internet, and another interface for booting the MAAS machines (unless there is a beter/more best-practice method of doing this)
[13:39] <mup> Bug #1604424 opened: [2.0 RC2] The proxy server could not handle the request  /MAAS/api/2.0/machines/ -- urllib2.HTTPError: HTTP Error 502: Proxy Error  <oil> <MAAS:New> <https://launchpad.net/bugs/1604424>
[13:41] <ram_> roaksoax: Hi I tried as you said. I was unable to SSH to MAAS slave nodes. It has given permission denied(public key) Issue. In MAAS UI i added correct public key of MAAS server.
[13:45] <ram_> roaksoax: http://paste.openstack.org/show/537431/
[13:51] <mup> Bug #1604424 changed: [2.0 RC2] The proxy server could not handle the request  /MAAS/api/2.0/machines/ -- urllib2.HTTPError: HTTP Error 502: Proxy Error  <oil> <MAAS:New> <https://launchpad.net/bugs/1604424>
[14:00] <mup> Bug #1604424 opened: [2.0 RC2] The proxy server could not handle the request  /MAAS/api/2.0/machines/ -- urllib2.HTTPError: HTTP Error 502: Proxy Error  <oil> <MAAS:New> <https://launchpad.net/bugs/1604424>
[14:35] <acovrig> I seem to have this bug (https://bugs.launchpad.net/maas/+bug/1604128) however, I’m running MAAS 2.0.0 (rc2+bzr5156)
[14:37] <acovrig> installed from this PPA: http://ppa.launchpad.net/maas/next/ubuntu xenial/main amd64 Packages
[14:40] <roaksoax> acovrig: the fix has been made available in Ubuntu
[14:41] <acovrig> roaksoax: what do you mean?
[14:41] <roaksoax> acovrig: that it is in -updates
[14:41] <roaksoax> acovrig: but I'm guessing that your version number is different from what's in the archive which is preventing the update
[14:41] <acovrig> so replace the ppm with maas/updates instead of maas/next?
[14:41] <roaksoax> acovrig: i'll make a fix available in maas/next
[14:42] <roaksoax> acovrig: no, I mean ubuntu archives, xenial-updates
[14:42] <acovrig> oh, I see; apt-cache shows 2.0.0~rc2+bzr5156-0ubuntu1~16.04.2, should I apt-get install maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 ?
[14:57] <roaksoax> acovrig: if you can try that and tell me if it works ?
[14:57] <roaksoax> acovrig: i'm uploading a new version on the PPA too
[14:57] <acovrig> sudo apt update && sudo apt upgrade doesn’t show any updates
[14:58] <roaksoax> acovrig: i'm uploading to the ppa nowish
[14:58] <roaksoax> acovrig: should be aailable in ~30 mins tops
[15:00] <acovrig> roaksoax: just curious, would apt-get install maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 solve my issue?
[15:03] <roaksoax> acovrig: it should, but i've not tried it
[15:03] <roaksoax> acovrig: i'd suggest for you to wait for the update in PPA
[15:05] <acovrig> roaksoax: yea, I’m planning on waiting
[15:12] <mup> Bug #1604460 opened: In Node details->Machine output->Commissioning output the filename is hidden <ui> <MAAS:New> <https://launchpad.net/bugs/1604460>
[15:12] <mup> Bug #1604461 opened: [2.0 RC2]  regiond log errors: duplicate key value violates unique constraint "maasserver_staticipaddress_ip_key" DETAIL:  Key (ip)=(**.***.**.**) already exist <oil> <MAAS:New> <https://launchpad.net/bugs/1604461>
[15:42] <acovrig> roaksoax: apt update && apt upgrade is what I should be doing, right; I don’t see the update yet
[15:44] <acovrig> roaksoax: OK, it shows up now, update pending
[15:47] <acovrig> roaksoax: I updated (2.0.0~rc2+bzr5156-0ubuntu2~16.04.2) and still get “Invalid SSH public key: 'PosixPath' object has no attribute 'path'“
[16:00] <mup> Bug #1604465 opened: [2.0rc2] RackController.get_image_sync_status causes huge load on regiond process <oil> <MAAS:Triaged> <https://launchpad.net/bugs/1604465>
[16:07] <roaksoax> acovrig: are you truing to add via the webui ?
[16:08] <acovrig> roaksoax: yes
[16:10] <acovrig> roaksoax: I have a VM running ubuntu 16.04 and maas 2.0.0~rc2+bzr5156-0ubuntu1~16.04.1 and it accepted the key…
[16:12] <roaksoax> acovrig:that's strange
[16:12] <roaksoax> acovrig: so it accepted the key with  2.0.0~rc2+bzr5156-0ubuntu1~16.04.1 but not the one from PPA ?
[16:13] <acovrig> the VM was installed from http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 (apt-cache policy maas)
[16:14] <acovrig> roaksoax: I see the same version in apt-cache (http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64) in the non-working server, should I attempt to list all the dependencies to ‘cross-grade’ to that ‘version’?
[16:17] <acovrig> roaksoax: do you think apt-get remove maas && apt-get install maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 would work and keep my config?
[16:17] <acovrig> (with an apt-get autoremove in between)
[16:18] <roaksoax> acovrig: it should keep your config, let me test something though
[16:25] <roaksoax> acovrig:  sudo apt-get install maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 python3-maas-client=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-cli=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-common=2.0.0~rc2+b
[16:26] <roaksoax> zr5156-0ubuntu1~16.04.2 python3-django-maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-dhcp=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-proxy=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-dns=2.0.0~rc2+bzr5156-0ub
[16:26] <roaksoax> untu1~16.04.2 maas-region-api=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-region-controller=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 python3-maas-provisioningserver=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-rack-
[16:26] <roaksoax> controller=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2
[16:26] <roaksoax> acovrig:  sudo apt-get install maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 python3-maas-client=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-cli=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-common=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 python3-django-maas=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-dhcp=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-proxy=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-dns=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-region-api=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-regio
[16:26] <roaksoax> acovrig: ok, that sould work
[16:30] <acovrig> roaksoax: Unable to locate package maas-regio and had to add maas-rack-controller=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 maas-region-controller=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 python3-maas-provisioningserver=2.0.0~rc2+bzr5156-0ubuntu1~16.04.2 but it accepted the install then; currently installing, then will try the key again
[16:32] <roaksoax> acovrig: that's a paste issue
[16:34] <acovrig> yea, figured as much; *sigh* _still_ installing lol
[16:41] <acovrig> roaksoax: same issue, I tried from a browser that has never seen MAAS so it’s not a chache issue on the browser side; could the key be partially imported somwhere on the backend?
[16:48] <roaksoax> acovrig: what if you manually restart maas-regiond and maas-rackd ?
[16:48] <roaksoax> acovrig: actually, only maas-regiond
[16:48] <acovrig> roaksoax: sudo service maas-regiond restart I presume?
[16:48] <acovrig> same issue
[16:51] <roaksoax> acovrig: weird
[16:51] <acovrig> roaksoax: yea, I’m starting to get the ‘defying logic’ feeling…
[16:52] <roaksoax> acovrig: that;s the diuff between version
[16:52] <roaksoax> https://launchpadlibrarian.net/273938668/maas_2.0.0~rc2+bzr5156-0ubuntu1~xenial1_2.0.0~rc2+bzr5156-0ubuntu2~16.04.2.diff.gz
[16:52] <roaksoax> acovrig: actually I see where the issue is
[16:52] <roaksoax> acovrig: let me fix it
[16:54] <mup> Bug #1558314 changed: maas server is overloaded - twistd and postgres processes > 200% <oil> <MAAS:Invalid> <https://launchpad.net/bugs/1558314>
[16:58] <roaksoax> acovrig: uploaded a new package. Let's see if that fixes it
[17:04] <acovrig> roaksoax: apt update && apt-cache policy shows it wanting to upgrade to 2.0.0~rc2+bzr5156-0ubuntu2~16.04.2; update running now
[17:13] <acovrig> O.o still get the same error… is there a md5sum I can check somewhere to sanity-check that the updates are installing propperly?
[17:25] <acovrig> roaksoax: if it means anything, the working system was installed from the ubuntu 16.04 server iso w/the MAAS option picked on boot, the non-working system was installed from the mini iso (netinstall)
[17:30] <acovrig> roaksoax: I updated the VM (was working system) and now I get the same error...
[18:16] <mup> Bug #1604513 opened: Redfish power support <MAAS:New> <https://launchpad.net/bugs/1604513>