[00:46] <pmatulis> San...
[08:32] <mwhudson> oy you guys maas ftbfs with python 3.6: https://launchpadlibrarian.net/318957048/buildlog_ubuntu-artful-amd64.maas_2.2.0~rc3+bzr6025-0ubuntu1_BUILDING.txt.gz
[13:06] <roaksoax> mwhudson: that seems due to changes with python deps
[14:59] <mup> Bug #1689838 opened: 'ValidationError' object has no attribute 'error_dict' <MAAS:Triaged> <https://launchpad.net/bugs/1689838>
[15:02] <mup> Bug #1689838 changed: 'ValidationError' object has no attribute 'error_dict' <MAAS:Triaged> <https://launchpad.net/bugs/1689838>
[15:05] <mup> Bug #1689838 opened: 'ValidationError' object has no attribute 'error_dict' <MAAS:Triaged> <https://launchpad.net/bugs/1689838>
[16:35] <mup> Bug #1689852 opened: [2.2RC3] MAAS doesn't handle switching BIOS from Legacy to UEFI <MAAS:New> <https://launchpad.net/bugs/1689852>
[20:48] <sanjay> Hello
[20:49] <sanjay> I required help in deploying nodes on MAAS
[20:49] <sanjay> anyone please help me in troubleshooting
[20:54] <stokachu> mpontillo: ^ may be network related
[20:54] <sanjay> i am able to connect to node while deploying and also can ping external network (www.google.com)
[20:58] <sanjay> hi
[21:01] <stokachu> sanjay: please be patient someone will get back to you
[21:01] <stokachu> sanjay: also a good idea is to run `sosreport` on your maas server
[21:03] <sanjay> ok fine
[21:30] <sanjay> hello
[21:49] <xygnal> mpontillo: any way to clear the old devices discovered in Device Discovery?  Those systems do not exist anymore, but they are still in there with their original discover dates.
[21:50] <xygnal> mpontillo: failing any CLI or UI method, what table are they kept in? :)
[21:51] <mpontillo> xygnal: yeah, there is a 'discoveries clear all=true' API/CLI command. We're thinking about better ways to age out discoveries for MAAS 2.3
[21:53] <mpontillo> sanjay: I'm on a plane right now so it's difficult to be of much help. ;-) but can you go into more detail about the problem you're having?
[22:06] <sanjay> ok
[22:06] <sanjay> thanks mpontillo for the same
[22:24] <mup> Bug #1689954 opened: MAAS running in snap fails to start ntpd when host OS has ntp running <error-surface> <notifications> <MAAS:New> <https://launchpad.net/bugs/1689954>
[22:25] <mpontillo> xygnal: if you wish to selectively clear things out, you may safely do so by deleting from the maasserver_neighbour table, IIRC
[22:26] <mpontillo> sanjay: so what exactly is the problem?
[22:26] <sanjay> ok
[22:26] <mpontillo> sanjay: have you set up a dynamic IP range on the subnet you want to manage and enabled DHCP on the VLAN?
[22:27] <sanjay> It assign a dynamic IP..
[22:31] <sanjay> curtin is also installed successfully
[22:32] <sanjay> after installation of OS on node it disconnect and then it say failed deployment
[22:34] <sanjay> Also out of 4 nodes, i have already deployed in 1 node and for other 3 i m not able to
[22:35] <sanjay> its the same mass, with same settings
[22:57] <mup> Bug #1689959 opened: MAAS running in a snap reports the wrong operating system/release <snap> <MAAS:New> <https://launchpad.net/bugs/1689959>
[23:00] <mup> Bug #1689959 changed: MAAS running in a snap reports the wrong operating system/release <snap> <MAAS:New> <https://launchpad.net/bugs/1689959>
[23:03] <mup> Bug #1689959 opened: MAAS running in a snap reports the wrong operating system/release <snap> <MAAS:New> <https://launchpad.net/bugs/1689959>
[23:09] <sanjay> PXE Request - local boot, Installation complete - Node disabled netboot
[23:35] <sanjay> maas nodes failed after timout of 60 min
[23:35] <sanjay> even if i increase to 4 hrs its also getting failed
[23:36] <sanjay> also i m not able to see the log error
[23:36] <sanjay> so that i can search on net
[23:42] <sentinel_> hmmmm
[23:43] <sentinel_> so i could use a bit of help
[23:44] <sentinel_> i am new to maas and am just trying to get it to work right at this point
[23:46] <sentinel_> and it's probably me doing something dumb
[23:47] <sentinel_> anyone here posably able to help?