[15:51] holmanb: falcojr upstream 23.3 is good for review and includes ec2/mantic integration test fixes [15:51] https://github.com/canonical/cloud-init/pull/4388 [15:51] -ubottu:#cloud-init- Pull 4388 in canonical/cloud-init "Release 23.3" [Open] [18:21] [community notice] Release of cloud-init 23.3 published. Thanks again for all the hard work!!! https://github.com/canonical/cloud-init/releases/tag/23.3 === blackboxsw changed the topic of #cloud-init to: 23.3 Released 08/28 | File bug: https://github.com/canonical/cloud-init/issues/new/choose | PRs: https://git.io/JeVed | release schedule: https://discourse.ubuntu.com/t/2023-cloud-init-release-schedule/32244 [18:25] great news [18:39] falcojr: holmanb https://github.com/canonical/cloud-init/pull/4391 for upload to Ubuntu mantic development release [18:39] -ubottu:#cloud-init- Pull 4391 in canonical/cloud-init "Ubuntu/devel" [Open] [20:01] I need to submit an update for the ports [20:01] and a report [20:08] qq re: network-config. Is the "id0 match:" stuff in the docs expected to work for all Linux OS, or just Ubuntu? I'm having issues on Debian and just wanted to rule out the obvious. [20:09] network-config file here: https://paste.opendev.org/show/821328/ [22:46] inflatador: from the docs https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.ht [22:46] oop,s https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html#common-properties-for-physical-device-types [22:46] "Note that currently only networkd supports globbing, NetworkManager does not." [22:50] meena: was chatting to someone in another channel who is trying to get c-i working with OpenBSD and hit some issues [22:50] minimal: oy [22:51] i have neglected OpenBSD quite a bit, since it's not really a daily environment for me. [22:51] what problems where they having? [22:51] meena: the current one they're seeing (now that they're trying 23.3) is that, unlike for freebsd, there is not specific netbsd or openbsd code for running "dhclient" and so options are being used that are not supported by OpenBSD dhclient [22:52] unlike FreeBSD's dhclient apparently OpenBSD's does not support either "-l" or "-p" (and also doesn't support "-1" that __init__.py tries) [22:54] good grief, how do they have an even older code base than we do?? [22:54] ours is from like 1997 [22:55] I#m just going from https://man.openbsd.org/dhclient.8 [22:55] the point is currently FreeBSD dhclient is handled by freebsd.py, for netbsd and openbsd it is not [22:55] and the "standard" option of "-1" is not recognised by OpenBSD [22:56] aye [22:56] i don't even see a dhclient man page for netbsd. [22:56] haven't checked that, was only helping them with openbsd [22:56] aye. [22:57] can they open a bug, and I'll take a look at this tomorrow, when I'm not a meter and a half in nroff and virtio code? [22:58] they had earlier problems (i.e. iproute being used) until they moved to 23.3 so obviously those were addressed by your recent changes [22:58] (btw, i was gonna steal some baseline virtio documentation from NetBSD or OpenBSD, but it turns out, they have as much virtio documentation as FreeBSD) [22:59] minimal: i really didn't think that there could be an Operating system out there with an older dhclient codebase, with even less options with FreeBSD, so I didn't even bother checking. [23:00] they're hoping to work on cloud-init packaging for OpenBSD [23:01] I've pinged them to open a github issue but they're "idle" currently [23:07] minimal: they could also join this channel… [23:08] anyway, i think i'm giving up on documentation for tonight, and will try again tomorrow. brain is not cooperating. [23:08] yes ~I was going to suggest that once they're no longer idle