[07:54] <mup> Bug #1781361 opened: Updating 'service_set' of rack controller using API <MAAS:New> <https://launchpad.net/bugs/1781361>
=== wiro_ is now known as wiro
[13:28] <mup> Bug #1781361 changed: Updating 'service_set' of rack controller using API <MAAS:Invalid> <https://launchpad.net/bugs/1781361>
=== frankban is now known as frankban|afk
[19:17] <mup> Bug #1781464 opened: [2.5] When running unit tests, MAAS log should be printed to the console <MAAS:Triaged> <https://launchpad.net/bugs/1781464>
[19:40] <xygnal_> we cant seem to run recent centos images without cloud-init failing to finish/check into maas.
[19:40] <xygnal_> did anything change? old images seem to work
[19:47] <mup> Bug #1772616 changed: Duplicate MAC or hostname causes MAAS to confuse rack controllers <sts> <MAAS:Opinion> <https://launchpad.net/bugs/1772616>
[19:53] <mup> Bug #1772616 opened: Duplicate MAC or hostname causes MAAS to confuse rack controllers <sts> <MAAS:Opinion> <https://launchpad.net/bugs/1772616>
[19:56] <mup> Bug #1772616 changed: Duplicate MAC or hostname causes MAAS to confuse rack controllers <sts> <MAAS:Opinion> <https://launchpad.net/bugs/1772616>
[20:06] <roaksoax> xygnal_: what cloud-init version is that ?
[20:06] <roaksoax> xygnal_: are these the maas provided images ?
[20:07] <roaksoax> xygnal_: also, did you ever transition to 2.4 ?
[20:09] <xygnal_> yes we are 2.4.  that is when the problem started.
[20:10] <roaksoax> xygnal_: i woudl check that /etc/maas/rackd.conf points to the right IP first
[20:10] <xygnal_> not untouched cents image, but based off it with no modifications to cloud init.
[20:10] <xygnal_> that would cause old images to deploy but not new ones?
[20:11] <roaksoax> xygnal_: no not really. Unless the new images are missing a driver or something along the lines
[20:12] <roaksoax> xygnal_: but that said, looking at our CI jobs
[20:12] <roaksoax> xygnal_: i can confirm that the last centos test run was 11 hours ago, and no issues
[20:12] <xygnal_> just checked.  ip is correct.
[20:13] <xygnal_> we also caught the new image trying to connect to the internet for centos repos we did NOT add ourselves
[20:13] <xygnal_> which we had not witnessed before
[20:14] <xygnal_> whh
[20:14] <xygnal_> which could never work, firewall
[20:17] <xygnal_> what do maas built in proxy settings cover and not cover?
[20:26] <mup> Bug #1771885 opened: bionic: static maas missing search domain in systemd-resolve configuration <bionic> <network> <cloud-init:Won't Fix> <juju:Fix Released by ecjones> <juju 2.3:Fix Released by ecjones> <MAAS:New> <MAAS 2.3:New> <MAAS 2.4:New> <https://launchpad.net/bugs/1771885>
[20:31] <roaksoax> xygnal_: the built in proxy is just a caching proxy really