[15:08] <holman> meena: thanks for sharing, good stuff
[15:09] <holman> meena: i know you had a link to it before but i forgot to bookmark it, how to start a freebsd image in lxd manually
[15:10] <holman> There was an extra step to avoid a CPU being eaten by the freebsd kernel
[15:10] <meena> i would hope that's fixed by now in 14.0
[15:10] <meena> or, lemme check
[15:10] <holman> Okay I haven't checked yet on that
[15:10] <holman> It might be
[15:11] <holman> minimal: thanks for filing the test failures
[15:11] <holman> Reminds me I'd love to see an alpine unit test run in our ci to catch stuff like this
[15:14] <meena> holman: yeah: this is *in* 14 https://freshbsd.org/freebsd/src/commit/f1c5a2e3a625053e2b70d5b1777d849a4d9328f2
[15:15] <meena> i haven't had any issues with virtio_random in quite some time now
[15:15] <meena> i forgot how painful it's been
[15:16] <meena> but I wonder if it's in 13.x
[15:18] <minimal> holman: np, I hit a 3rd testcase fail but #5082 was already raised that addressed it
[15:19]  * meena is currently trying to see through a forest of pointers and will hopefully emerge from that with some brain cells intact
[15:20] <minimal> holman: I'm only getting back into cloud-init dev now as I had to spend the past couple of weeks restructuring how I build things etc now that I'm not directly involved in Alpine
[15:46] <holman> minimal: no worries - understood
[15:46] <holman> minimal: I'm glad you're still around :-)
[15:54] <minimal> yeah I still have a list of stuff to add to or fix in cloud-init ;-)
[15:54] <blackboxsw> This is great to hear minimal that you're still involved && engaged.
[15:56] <meena> https://github.com/canonical/cloud-init/issues/5096 maybe then I would know what kubernetes is…
[15:56] -ubottu:#cloud-init- Issue 5096 in canonical/cloud-init "Kubernetes example" [Open]
[15:57] <minimal> blackboxsw: I always intended to stay engaged with cloud-init, it's just that Alpine "politics" complicated things
[15:58] <blackboxsw> ... it's a shame about that. Yes we had heard through Brett. (and your historical representation of that context a bit a while back)
[15:58] <minimal> the alpine cloud-init & cloud-utils packages are currently without a maintainer and I suspect that won't change for some time, if at all
[16:46] <blackboxsw> holman: falcojr: I was unable to reproduce any issues with Vultr per https://github.com/canonical/cloud-init/pull/4986. Launches look "good" and only interesting issue I saw from 23.3.3 -> 23.4.4 upgrade was the warning about scripts/vendor directory not being executable, which is already fixed in tip of main.
[16:46] -ubottu:#cloud-init- Pull 4986 in canonical/cloud-init "fix: Don't warn on vendor directory" [Merged]
[16:47] <blackboxsw> wrong link: https://github.com/canonical/cloud-init/issues/5092
[16:47] -ubottu:#cloud-init- Issue 5092 in canonical/cloud-init "cloud-init upgrade causes vultr init networking to fail." [Open]