[14:58] <caribou> Hello, me again with a new IPv6 related question : When using the EphemeralIPNetwork() class, with ipv4=True, ipv6=True, is each IP version used sequentially ?
[14:59] <caribou> I mean if I use this decorator, IPv4 will be tried first right ?
[15:01] <aciba> caribou: ipv4 first and then ipv6, both versions used: https://github.com/canonical/cloud-init/blob/c273d0e9f262d61b275369ce5587151b0df0dfe6/cloudinit/net/ephemeral.py#L442
[15:01] <caribou> aciba: thanks for the confirmation
[15:07] <caribou> I also see that both the DataSourceEC2 & DataSourceOpenStack make use of the url_helper.wait_for_url() with a list of IPv4 & IPv6 metadata URLs. This is based on the assumption that either IPv4 or both IPv4 & IPv2 stack will be available as I understand it
[15:07] <caribou> for a bit of background, I'm working on the IPv6 impleplentation of our DataSourceScaleway
[15:08] <caribou> s/impleplentation/implementation/
[15:16] <aciba> caribou: per the documentation of EphemeralIPNetwork, if ipv4 and ipv6 are set to true then the assumptions are (ipv4 and ipv6) or (ipv6 only)
[15:16] <caribou> ok, thanks for the clarification
[15:21] <caribou> btw, which documentation are you referring to ?
[15:22] <aciba> https://github.com/canonical/cloud-init/blob/c273d0e9f262d61b275369ce5587151b0df0dfe6/cloudinit/net/ephemeral.py#L439
[15:22] <caribou> thanks!
[15:22] <aciba> and the error handling in the except block
[15:24] <caribou> aciba: if I read it right, it is "Only IPv4" or "Dualstack IPv4 and IPv4"
[15:25] <caribou> s/and IPv4/IPv6/
[15:28] <caribou> aciba: thanks for the fix on LP: #2003562 btw
[15:28] -ubottu:#cloud-init- Launchpad bug 2003562 in cloud-init (Ubuntu) "network-manager renderer does not honour IPv6 default route subnet" [High, Fix Committed] https://launchpad.net/bugs/2003562
[19:42] <sstory> Trying to setup on RockyLinux 8.7 for a proxmox template. Getting some errors in cloud.cfg
[19:44] <sstory> https://paste.centos.org/view/1d945402 Any ideas how to make it not freak out over the colon. I am new to this.
[19:50] <waldi> sstory: this is not valid yaml, it needs some ":"
[19:56] <sstory> waldi: Wow! I could NOT see the : missing after sudo!  Amazing what another pair of eyes can do
[23:30] <meena> minimal: current status: trying to test your patch
[23:31] <meena> step one: build cloud-init with your patch…
[23:32] <meena> step zero: upgrade all VMs i haven't touched in 2 months
[23:41] <meena> i also need to generate a certificate chain
[23:46] <minimal> meena: thanks
[23:46] <minimal> you can use openssl to create a cert
[23:47] <meena> minimal: i know, i just need to remember the secret invocations again
[23:47] <minimal> meena: I have scripts for that to create root and intermediate CAs ;-)
[23:48] <meena> minimal: i have shed the need for such things long ago
[23:49] <minimal> BTW best to test using throwaway VMs, especially for testing the delete certs functionality - if it works then anything relying on the CA certs will fail (e.g wget, curl, package manager perhaps, etc)
[23:49] <minimal> meena: rather than rely on scripts you rely on your memory? lol
[23:50] <meena> minimal: i have shed memory, too, pretty sure my brain's gone out the window with covid
[23:53] <meena> are we still generating RSA keys?
[23:57] <minimal> for what exactly? certs? that depends on what the certs might be used for.