[12:44] <paride> Odd_Bloke, hi! We've been seeing this error: https://paste.ubuntu.com/p/4kjf5rfQf7/ in the cloud-init-ci-nightly testing since https://github.com/canonical/cloud-init/commit/66e114a660c53400e389f119781f378311b65108 landed
[12:44] <paride> same error lucasmoura mentioned yesterday in his triage
[12:46] <paride> fixing it could be as easy as adding a missing dep, but I can't find the right one
[12:46] <paride> maybe it is something you know already?
[12:46] <Odd_Bloke> paride: Yep, I can dig into it!
[12:53] <Odd_Bloke> paride: Oh, I think we dropped that job from config when we migrated to GH.
[12:54] <Odd_Bloke> paride: So I think it just needs deleting from Jenkins?
[12:54] <Odd_Bloke> paride: Specifically in https://github.com/canonical/server-jenkins-jobs/commit/3036d11d8955c48fc7e8025704d2a1d98c5632b5
[12:55] <paride> Odd_Bloke, I was coming to the same conclusion :) I deleted them from the jjb config but not from jenkins
[12:55]  * paride proceeds to the deletion
[12:55] <paride> Odd_Bloke, thanks!
[12:56] <paride> there, one less red job
[12:56] <Odd_Bloke> (As an aside, the fix would have been to add `--release xenial` to the `bddeb` call, so that the xenial-specific dependency is added to Build-Depends as in https://github.com/canonical/cloud-init/commit/66e114a660c53400e389f119781f378311b65108#diff-354f30a63fb0907d4ad57269548329e3)
[13:22] <Odd_Bloke> rharper: Not sure if you're around given the 4th, but do you have any thoughts on next steps for https://bugs.launchpad.net/cloud-init/+bug/1874544?
[15:44] <rharper> Odd_Bloke: if we must fix the ib double mac issue on our side; then it's just a matter of ignoring duplicate macs when the interface type is infiniband;  Azure really should fix the platform which is duplicating the hv_net mac into the ib device; but I don't expect that to change any time soon;
[16:01] <Odd_Bloke> rharper: Thanks!
[16:05] <compufreak> How should /meta-data work for nocloud-net? I tried to model it after AWS but it looks like it requests /meta-data and expects it to return yaml whereas AWS returns text/plain list of keys
[16:07] <compufreak> ahh, nocloud-net expects yaml--finally found it in the docs
[16:16] <Odd_Bloke> compufreak: :) Let us know if you have any follow-up Qs!
[16:41] <meena> Odd_Bloke, rharper, : on a "standard Bionic image" — my first thought was, blame the image…
[17:44] <Odd_Bloke> meena: I'm missing some context here. :)
[18:59] <meena> Odd_Bloke: re https://bugs.launchpad.net/cloud-init/+bug/1874544
[19:25] <MICROburst> How to enable disk encryption/LUKS and have cloud-init asking for the passphrase?
[19:33] <Odd_Bloke> MICROburst: cloud-init doesn't really "ask" users for anything, could you explain what you're looking to do a little more?
[19:37] <Odd_Bloke> meena: Aha, right; nope, just giving us something concrete that we can confirm a reproducer/fix with. :)
[19:42] <MICROburst> Odd_Bloke: I would like to use one system for all. On Fedora I was using kickstart, but now I'm about to migrate to Ubuntu. so cloud-init should do the job on bare metal too.
[19:54]  * meena mumbles something about preseed
[20:00] <Odd_Bloke> MICROburst: cloud-init isn't designed for installing systems, it customises pre-built images (such as those used for cloud instances).  You might be looking for something like subiquity autoinstalls: https://ubuntu.com/server/docs/install/autoinstall-reference ?
[20:01] <Odd_Bloke> (You'll notice that you can pass cloud-init configuration to subiquity, if there is cloud-init functionality you would like to use that isn't covered by subiquity's own configuration.)
[21:31] <MICROburst> Looks like a hen and egg problem: https://discourse.ubuntu.com/t/cloud-init-and-the-live-server-installer/14597 https://discourse.ubuntu.com/t/please-test-autoinstalls-for-20-04/15250 -- ubuntu is referring to cloud-init - there is little or not description for subiquity