[10:46] <meena> oh cool, you can't actually do that.
[11:24] <meena> okay, i have duplicated the effort, and now i have two failing test-cases, because the two code-paths have divergent behaviour
[11:24] <meena> or, at least they do in the code.
[11:43] <meena> either way, it fixes the actual thing we were trying to fix…
[11:43] <meena> Now I just need to figure out how to fix the tests.
[11:44] <meena> After a short intermission of getting LXD agent to compile on FreeBSD.
[11:57] <Ani> Can someone please review https://github.com/canonical/cloud-init/pull/2142 ?
[11:57] -ubottu:#cloud-init- Pull 2142 in canonical/cloud-init "Do not generate dsa and ed25519 key types when crypto FIPS mode is enabled" [Open]
[14:01] <holmanb> meena: yeah this noexec code was a series of workarounds for Linux images that were "hardened" by making certain partitions noexec. I think it was initially for the DHCP sandbox thingy, but I recall that something else depends on it too (maybe the puppet module? Idk)
[14:03] <holmanb> meena: while you're at it, have you seen the recent bug related to MBR + slices? We have some regard that's failing related to that too
[14:22] <meena> holmanb: i have seen the bug, but haven't gotten around to it yet
[14:39] <meena> holmanb: i'll look into it… but… i haven't had a system with MBR (and slices) in decades lol
[15:22] <falcojr> Community notice: On Tuesday, May 9th, cloud-init will move its upstream bug tracking from Launchpad to Github. More details can be found at https://discourse.ubuntu.com/t/cloud-init-migrating-to-github-issues/35432
[16:15] <minimal> falcojr: before May 9th should new bugs still be opened on Launchpad rather than Github?
[16:16] <falcojr> Yep, still Launchpad until then