[21:24] nice powersj thanks for ubuntulog2 [21:24] that should do it [21:33] i think the changes that rharper requested are already in. [21:33] (and smoser approved…) [22:00] that pull request was kinda crazy [22:00] ending up in like 10 lines of code and 30 of test ;) [22:03] Odd_Bloke, fyi I updated rtd to use github and confirmed the build works [22:04] it was still pointing at our launchpad url [22:04] https://cloudinit.readthedocs.io/en/latest/topics/security.html now shows up [22:05] powersj: Great! [22:07] aaaaaaand another one: https://github.com/canonical/cloud-init/pull/93 [22:09] now to find out how to discourage https://bugs.launchpad.net/cloud-init/+bug/1855170 or document or whatever… [22:09] Ubuntu bug 1855170 in cloud-init "system_info can change the distro" [Undecided,New] [22:09] or perhaps just ask Hetzner to remove that damn distro line from their # cloud-config [22:23] interesting. meena on that bug, I'd expect that the cloud-platform should not be setting an opinion on what the distro is expected to be from metadata checking the details on that [22:24] the "system_info: distro specification is generally expected from the image filesystem" [22:24] blackboxsw: especially since they allow to override the installation via ISO 🤣 [22:24] if you had cloud-init query --all on the platform that exhibited that info that'd be cool [22:25] it *should* show all metadata consumed by cloud-init (I think) [22:25] sudo cloud-init query --all [22:25] * blackboxsw doesn't have a heztner account afaik [22:25] blackboxsw: https://gist.github.com/igalic/e637014696e7f0f8a69023a9fe873e15 [22:26] ignore the userdata [22:27] cloud-init hasn't gotten that far yet xD [22:29] nice puppet facts :) [22:29] anyhow, ok vendor data is what's setting ubuntu as distro potentially? [22:30] s/potentially?// [22:30] * blackboxsw needs to figure out a good oneliner to unmime unjson that vendordata content [22:41] blackboxsw: we could add a --decode flag to query ? [22:41] well, if i query only vendordata, you get something more useful [22:42] https://gist.github.com/d89bf0775ed9233987248d547929ac1f [22:42] nice paste meena thx [22:43] yeah I'd expect if you were launching a non-ubuntu instance, vendordata can't set distro: ubuntu that's busted [22:43] that sounds like a platform bug [22:44] what's all in vendor data? user-data can disable vendor data [22:44] rharper: oh? [22:44] wait a damn minute… where's the network config?! [22:45] oh, under network config [22:47] or not… [22:48] on my other server, running a very old version of cloud-init, i can query ds.meta_data.network_config [22:48] but not on this one :( [22:49] i wonder why [22:53] i think i'm gonna have a lot more patching to do [22:53] some other time. [22:54] Good night folks o/~ [23:10] on a bionic machine, trying to run cloud-tests and getting an error `No storage pool found. Please create a new storage pool`. any thoughts? i ran this example exactly: https://cloudinit.readthedocs.io/en/latest/topics/tests.html#treerun-and-treecollect (the tree_run) [23:12] by default we try to use LXD, that certainly sounds like you don't have lxd setup [23:12] ah yeah that's probably it [23:12] actually looks like lxd pkg is already installed [23:13] have you run lxd init? [23:13] Lxd unit then [23:13] Oops lxd init [23:15] looks like that might've done it [23:18] if i only want to run cloud-tests on azure, do i just comment out the ec2 config in platforms.yaml? [23:19] actually do i just set --build-platform to azurecloud then? [23:19] ah i bet that's what it is [23:19] chillysurfer, that should do it [23:19] powersj: nice thanks [23:19] we default the platform to lxd since it is fast and easier to run usually [23:19] and doesn't cost money :D [23:20] i'm going to see if the read_file_or_url regression (that was already fixed) is caught with cloud-tests