[00:40] <blackboxsw> azure run looks like it is going ok w/ new creds https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-bionic-azure/70/console
[00:47] <blackboxsw> I mean with new pycloudlib && handling jenkins workers without azure-cli installed
=== ananke_ is now known as ananke
=== blackboxsw is now known as blackboxsw_afk
[10:16] <aciba> blackboxsw: holmanb: https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-bionic-azure/70/ looks ok respect to the credentials problem. There are a couple of new ansible tests failing, but those are not new nor related to azure (see https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-kinetic-ec2/55/)
[12:16] <blackboxsw_afk> aciba: I think that run is ok as it was "Started 3 days 6 hr ago" before the ansible fixes.
[12:17] <blackboxsw_afk> we only need validate jenkins build runs which kicked off within the last 24 hours. (and hopefully kick off more manually, one per cloud, to get coverage)
=== blackboxsw_afk is now known as blackboxsw
[12:23] <blackboxsw> from the looks of jenkins timed runs are in progress right now for lxd_container/vm/gce and ec2. so hopefully some good results shortly
[13:46] <aciba> let's how they finish. About https://bugs.launchpad.net/cloud-init/+bug/1983306, I have created a PR here: https://github.com/canonical/cloud-init/pull/1644
[13:46] <ubottu> Launchpad bug 1983306 in cloud-init "schema validation not in line with specification" [High, In Progress]
[13:47] <ubottu> Pull 1644 in canonical/cloud-init "schema: Resolve user-data if --system given" [Open]
=== cpaelzer_ is now known as cpaelzer
[20:39] <ananke> this is a long shot, but I don't suppose anybody's familiar with how cloud-init works in conjunction with netplan? straight to the point though: I'm trying to execute custom code via dhclient's exit hooks, but that's not working on ubuntu (code does not execute at all. works fine on debian)
[20:40] <ananke> in the cloud-init logs I see that cloud-init copies and executes dhclient with its own set of options
[20:42] <ananke> and looks like its options are set to specify script to be /bin/true: 2022-08-09 20:19:02,244 - subp.py[DEBUG]: Running command ['/var/tmp/cloud-init/cloud-init-dhcp-0bf1kmdu/dhclient', '-1', '-v', '-lf', '/var/tmp/cloud-init/cloud-init-dhcp-0bf1kmdu/dhcp.leases', '-pf', '/var/tmp/cloud-init/cloud-init-dhcp-0bf1kmdu/dhclient.pid', 'ens5', '-sf', '/bin/true']
[20:48] <ananke> hah, so netplan points fingers at networkd-dispatcher: https://netplan.io/faq
[20:57] <ananke> hah. and I just figured out why I was getting poor results with networkd-dispatcher