[14:36] holman: i finally have an AMI that i can use to test cloud-init on AWS very easily! [14:36] (very easily == it only took a week to get there) [14:36] dch: ^ [15:12] meena: have you tried running cloudinit in a jail? seems silly but its possible [15:12] * dch wonders if there's a fake cloudinit-server daemon or if I should roll my own... [15:33] dch: I've seen a blog post somewhere of someone doing that [15:34] one of the big jail managers supports it [15:37] dch: there's this one, https://lseek-urandom.blogspot.com/2024/02/using-freebsd-jails-to-debug-cloud-init.html [15:39] right, and cbsd supports it too, but the stuff they support is rather inferior [15:53] meena: yay! [15:53] meena: glad to hear it! [15:53] holman: i finally gave that rundir change a run, and it works as expected [15:54] meena: thanks for testing that, glad we're making progress there [15:54] I'm just glad i finally got a pipeline for testing; it's arm64-only for now, but, eh [15:56] blackboxsw was out last week, and I expect he is wrapped up in 24.1 release work now [15:56] but if you haven't already could you mention in the PR that you tested it? [15:56] at this point the rundir PR depends on his review [15:57] we're currently uploading 24.1.2 stuff XD [15:57] awesome meena! And we just released 24.1.2 [15:57] blackboxsw: did it contain my last patch :O [15:58] for future reference: How do I ask for a patch to be included in a current release? [15:59] thx falcojr . yes uploads to -proposed should have queued in unapproved already `[ubuntu/mantic-proposed] cloud-init 24.1.2-0ubuntu1~23.10.1` just waiting on bot announcements in ubuntu-release [16:01] meena these point releases are mostly for breaking regressions from the previous release. Otherwise changes will wait till the next quarterly release. If you do find breaking changes, you can file a bug and call it out as such [16:02] it's not a breaking change, just the adduser thing that doesn't respect homedir [16:02] works now with my fix [16:02] cool [16:02] meena: at one week prior to a release `24.2` we'll ping with community-notice in IRC to request if there are PRs, bugs or features that need to be wrapped up prior to our next scheduled release. Generally we try to tag those bugs as 24.2 label and set priority label on them to ensure they aren't overlooked by next planned release. [16:03] so expect ping/communication around May 27 per our schedule in the topic of this channel https://discourse.ubuntu.com/t/2024-cloud-init-release-schedule/41679 [16:04] *nod* [16:05] I can, or should, carry this patch until then, given that it fixes real a issue [16:05] also in the weeks right after an upstream release we keep an eye out for any unforeseen regressions that warrant a hotfix as james alluded to. if something crtiical comes out just after 24.1 we go into hotfix mode to put in will-scoped fixes for this cases, no additional communication needed beyond the bugfiling and representation of criticality [16:05] yeah, no, this is and old bug [16:06] I could've fixed it earlier, but I only really started testing things when holman pinged me about the rundir changes [16:08] anyway, I'll get onto the growfs stuff, and then get back to wading knee deep in stuff I don't know (kernel code) [16:08] meena: I forgot to ping in IRC this cycle for the 24.1 release sorry about that [16:10] meena: curious how your testing workflow on Amazon looks, if you have any code or informal docs that you don't mind sharing [16:10] (don't feel like you have to put something together of course) [16:10] holman: i have shell code right now… would be nice to turn that into TerraForm / OpenTofu [16:11] lemme toss that onto a git thingy [16:16] meena: I'm technically not working until Friday but will be happy to take a look when I'm back online [16:26] holman: https://codeberg.org/meena/test-cloud-init [16:28] i guess i could also make my AMI public, so no one else has to go through the pain of doing that