[12:27] <cgd> Hi everyone I am trying to troubleshoot an issue. I am hoping that a cloud-init 'Elder' can impart some wisdom!
[12:30] <cgd> I am trying to install some packages but I get an error, according to output log file that it failed to connect to package server for download. I have had this issue more than once, I read it could have something to do with dynamically assigned IP addresses on network
[12:31] <cgd> Happy to give log output and yml file
[12:39] <jeeebz> Hello !
[12:41] <jeeebz> I'm not in the cloud domain, but someone asks for the cloud-init package. I wrote the spec and build the package for our distro, and I would like to know if there are other things to do more than compiling, packaging.
[13:23] <Odd_Bloke> cgd: What distro are you running?  How did you acquire/create the image?
[13:24] <jeeebz> I just got an answer, cloud-init is already integrated in the distro, but I didn't found it first... I spent time for nothing xD The distro is Mageia
[13:25] <jeeebz> (already for 6 years integrated in Mageia https://svnweb.mageia.org/packages/cauldron/cloud-init/current/SPECS/cloud-init.spec?view=log )
[13:25] <Odd_Bloke> jeeebz: Oh no, always frustrating when that happens!  Still, let us know if there's anything else we can help you with. :)
[13:26] <jeeebz> Odd_Bloke: I've no question about cloud-init now. An ISP provides box with embedded OSs,
[13:27] <jeeebz> one would like to port Mageia on their box (freebox delta)
[13:27] <jeeebz> now I'm learning about qcow2 images. Normaly, it's done with the cloud-init part.
[13:29] <jeeebz> But, Odd_Bloke, maybe updating the repo mentionning that Mageia also is supported ?
[13:33] <Odd_Bloke> jeeebz: Could you run `cloud-init query distro` on a Mageia instance and let me know what it returns?
[13:34] <jeeebz> Hum... I've no instance, (it is just my desktop OS now). Should I do the whole process, creating a VM etc ?
[13:34] <jeeebz> Or just installing it would be enough ?
[13:37] <Odd_Bloke> jeeebz: I wouldn't suggest installing it on a desktop, it might behave unexpectedly.  I've actually answered my own question by looking at the source you just pasted: it looks like Mageia support is patched into cloud-init at package build time in Mageia.  So I don't think we should update the upstream docs, because Mageia isn't supported upstream.  That said, if you have a way of reaching out to Mageia
[13:37] <Odd_Bloke> folks, we'd be glad to accept a PR which added such support.
[13:37] <Odd_Bloke> (It's specifically this line: https://svnweb.mageia.org/packages/cauldron/cloud-init/current/SPECS/cloud-init.spec?view=markup#l69 which installs this file: https://svnweb.mageia.org/packages/cauldron/cloud-init/current/SOURCES/mageia.py?revision=553373&view=markup)
[13:44] <jeeebz> OK, I will wrote an email to this mageian member https://svnweb.mageia.org/packages/cauldron/cloud-init/current/SOURCES/mageia.py?revision=553373&view=markup#l10
[14:27] <Odd_Bloke> blackboxsw_: I've either responded to or addressed all your review comments on https://github.com/canonical/cloud-init/pull/493
[16:32] <blackboxsw_> Odd_Bloke: thanks for the review do you have a dump of cloud-init query --all available from an oracle instance using your pr?
[16:32]  * blackboxsw_ can't find my creds and --compartment-id as it's been a long time since I've touched oracle api
[16:39] <Odd_Bloke> blackboxsw_: Yep, let me quickly pastebin.
[16:42] <Odd_Bloke> blackboxsw_: https://paste.ubuntu.com/p/hss7cG77Nq/ is what calling the datasource file (i.e. __main__) gives us, and https://paste.ubuntu.com/p/SvKkyg6JFP/ is what `cloud-init query -a` emits.
[16:43] <Odd_Bloke> I notice that the subplatform there is incorrect, I guess that must be cached from the initial boot of the instance somehow.
[17:33] <blackboxsw_> Odd_Bloke: I'm +1 on oracle v1
[17:33] <blackboxsw_> thanks
[17:34] <blackboxsw_> needs rebase/ci/merge etc