=== Guest2107 is now known as toolz [05:22] @falcojr thank you SOOO much for looking at the bug. And let me point out that I'm thoroughly embarrassed that I didn't even see the signed-by statement. I had cut and pasted that from the docker website and never looked at it. I didn't want to spam the bug report with "thank you" messages, but that was a great response. I'll for now leave it open as you've made the correction for the cause and for the security reasons it should === paride changed the topic of #cloud-init to: 21.2 (May 6) | file a bug: https://bugs.launchpad.net/cloud-init/+filebug | pull-requests: https://git.io/JeVed | meeting minutes: https://goo.gl/mrHdaj | next office hours: June 1 17:15 UTC [13:37] Hi! So cloud-init is now registered as a project on Libera, owning #cloud-init and the #cloud-init-* channel namespace [13:37] woohoo [13:38] I configured the channel to gave ops to rick_h and the committers, let me know if there's anything else to set/tweak [13:38] smoser is also on the list but currently not identified with the nickserv [13:39] once we agree everything looks good let's update the docs and notify people on the mailing list [13:46] i'm not? [13:46] smoser, `/whois smoser` doesn't show you as "Logged in as ..." [13:46] there [13:47] there. [14:27] paride: nice! [15:50] woooooo! [15:57] hi folks! [15:57] I've got a probably stupid question [15:58] is there any straight way, within cloud-init that it would retry for resolving the metadata url? [15:58] https://github.com/canonical/cloud-init/blob/master/cloudinit/sources/DataSourceEc2.py#L251 [15:58] like, I can just submit a patch for adding a for blah then retry if not [15:59] but just wanted to be sure it wasn't already there [16:00] @smoser o/ [16:05] retrying there should not really be necessary. and 'is_resolvable_url' only checks (i htink) if the url is actually resolvable... it doesnt check it at all. so if you gave an IP address i think it would be guaranteed to pass. [16:07] I'm hitting a case where there's intermitent dns issues [16:07] like, at some point it fails to resolve [16:08] so was thinking about adding such option for this usecase [16:08] its probably racing with something on system boot. [16:08] and fixing that, or fixing your dns server would be good options. [16:09] yeah, probably that