=== cpaelzer_ is now known as cpaelzer === otubo` is now known as otubo [14:54] blackboxsw: found the cause of the jenkins failures. https://github.com/canonical/cloud-init/blob/main/tests/integration_tests/datasources/test_lxd_discovery.py#L25 is setting the image for all future installs in the tests which means we're detecting the lxd datasource when we shouldn't be. I should be able to get a fix together fairly quickly === cpaelzer_ is now known as cpaelzer [15:44] blackboxsw: https://github.com/canonical/cloud-init/pull/1092 [15:44] Pull 1092 in canonical/cloud-init "testing: Remove calls to 'install_new_cloud_init'" [Open] [15:56] falcojr: approved ci still running [19:59] falcojr: thx for the merge of upstream release 21.4 and fixing CI. [20:27] blackboxsw: jammy https://github.com/canonical/cloud-init/pull/1095 [20:27] Pull 1095 in canonical/cloud-init "Ubuntu/devel" [Open] [20:37] falcojr looking over it now. I think versioning is ok/desired at this point. we know the dated version we will release, so no need to avoid appending it. [21:10] hrm need a fix to new-upstream-snapshot for this. one min [21:44] falcojr: and holmanb https://github.com/canonical/uss-tableflip/pull/78 [21:44] Pull 78 in canonical/uss-tableflip "new-upstream-snapshot: add --first-devel-upload param" [Open] [21:44] we need this option to perform our first official upload into jammy [22:08] thanks holmanb on the review, whoops. fixed. and pushed [22:09] @blackboxsw: I figured :) [22:09] @blackboxsw: doing some first-time setup stuff for the dependant tools then I'll be able to test it [22:10] figured as well :) [22:10] it's a good intro to using the tooling needed for releases [23:15] Any references to how can I disable hotplug cloud-init module ? [23:22] ashishbansal96: 21.4 was just released upstream today. It won't run anything hotplug related unless explicitly configured to. It'll make its way into Ubuntu in the next few weeks. In the mean time, you can "rm /etc/udev/rules.d/10-cloud-init-hook-hotplug.rules" [23:25] falcojr Thanks for the help! I'll remove that udev rule. Right now it's hogging lot of CPU due to lot of veth related operations being performed by our applications. [23:26] "It won't run anything hotplug related unless explicitly configured to. It'll make its way into Ubuntu in the next few weeks" -- glad to hear that.