[01:12] <mup> Bug #1704026 opened: [2.3] Strange error when registering external rack controller <MAAS:Triaged> <https://launchpad.net/bugs/1704026>
[01:24] <mup> Bug #1704026 changed: [2.3] Strange error when registering external rack controller <ha> <MAAS:Triaged> <https://launchpad.net/bugs/1704026>
[01:30] <mup> Bug #1704026 opened: [2.3] Strange error when registering external rack controller <MAAS:Triaged> <https://launchpad.net/bugs/1704026>
[01:48] <mup> Bug #1704028 opened: [2.3] Registering a second region api causes strange traceback <MAAS:New> <https://launchpad.net/bugs/1704028>
[01:57] <mup> Bug #1704028 changed: [2.3] Registering a second region api causes strange traceback <MAAS:New> <https://launchpad.net/bugs/1704028>
[02:00] <mup> Bug #1704028 opened: [2.3] Registering a second region api causes strange traceback <MAAS:New> <https://launchpad.net/bugs/1704028>
[16:07] <agrebennikov> ltrager, hello, did you have a chance to play around the issue we discussed yesterday?
[16:30] <roaksoax> agrebennikov: he is investigating
[16:55] <mup> Bug #1704176 opened: [2.3] django.core.exceptions.ValidationError: ['xenial has no kernels available.'] <MAAS:Triaged> <https://launchpad.net/bugs/1704176>
[17:16] <mup> Bug #1664822 changed: [2.2] MAAS IPMI autodiscover should enable IPMI-over-LAN if disabled <MAAS:Fix Committed by andreserl> <MAAS 2.2:Triaged by andreserl> <https://launchpad.net/bugs/1664822>
[17:35] <agrebennikov> great, thanks roaksoax
[18:23] <ltrager> agrebennikov: So in my environment I blocked all network access and configured commissioning to use a proxy for apt so packages could still be installed
[18:24] <ltrager> agrebennikov: that worked fine I'm trying to break DNS for everything but the archives to see if thats it
[18:38] <ltrager> agrebennikov, roaksoax: So I disabled DNS and only allowed access to the archive via a proxy and commissioning and ntp testing all work fine, no systemd slow downs
[18:41] <agrebennikov> ltrager, what do you see in the syslog in the node?
[18:42] <agrebennikov> I mean complaints from systemd-tymesync regarding ntp.ubuntu.com
[18:44] <ltrager> agrebennikov: I actually don't have entries for ntp.ubuntu.com, on the settings page can you see if 'Use external NTP servers only' is checked?
[18:44] <agrebennikov> yes, I did that
[18:45] <agrebennikov> but even with that I have lots of complaints specifically from systemd-timesync
[18:45] <agrebennikov> which still wants to connect to ntp.ubuntu
[18:45] <ltrager> agrebennikov: are you using the latest images from http://images.maas.io/?
[18:45] <agrebennikov> I assume so since from what I understand it checks for new images constantly
[18:46] <agrebennikov> and I see it in the log of either region or rack controller
[18:46] <ltrager> agrebennikov: okay I was just checking if you were using mirrored images
[18:47] <agrebennikov> I'm going to rebuild my maas node right now since the entire kvm host with that vm was destroyed
[18:47] <agrebennikov> unfortunately...
[18:47] <agrebennikov> so I'll have fresh brand new installation in a couple of hours
[18:47] <agrebennikov> with the latest images
[18:48] <agrebennikov> and if I still observe same issue I'll try to gather the logs from it
[18:48] <ltrager> agrebennikov: ok if you run into the issue again could you try to install strace and run strace systemctl daemon-reload
[18:48] <agrebennikov> the problem is that the issue happens during the commissioning only
[18:49] <agrebennikov> once it failed and the tyme is synced - it works finr
[18:49] <agrebennikov> *fine
[18:49] <agrebennikov> but I'll try
[20:34] <mup> Bug #1704212 opened: MAAS marks node 'Deployed' before sshd is up <cdo-qa> <cloud-init:New> <MAAS:New> <https://launchpad.net/bugs/1704212>
[23:10] <agrebennikov> ltrager, will try my best once I got my jumphost back
[23:10] <agrebennikov> hopefully in an hour or so