blackboxswnoahm: thank you for raising that to our attention, I'm fixing the doc builds now and regenerating tagged releases03:24
blackboxswI did that early last week I believe, thinking I checked all the boxes on a docs migration to a readthedocs site that didn't have ads embedded.03:24
noahmblackboxsw: thank you! :) 04:04
blackboxswnoahm: reverted the migration temporarily so it won't redirect for the moment. most of the old builds fail on new RTD-hosted.com tooling. So, we'll sort how to export or migrate those static old builds before flipping the switch. noahm out of curiousity, how old a version were you interested in04:22
* blackboxsw was looking at making sure we sync back to 0.7.9 but not sure if we need to stretch farther04:25
noahmblackboxsw: I certainly don't anticipate needing anything further back than that. 19.3 is far enough for most of what I'm likely to care about.05:36
holmanbSuperLag: welcome :D11:47
holmanbSuperLag: ln 19 I was invoking cloud-init from a clone of the source code, on a system that has cloud-init installed that could be called as `cloud-init schema -c test.yml`, or using the --system flag instead of -c to check the schema on the system from the datasource rather than from a file.11:51
holmanbSuperLag: https://cloudinit.readthedocs.io/en/latest/reference/cli.html#schema11:51
holmanbSuperLag: https://cloudinit.readthedocs.io/en/latest/reference/faq.html#how-can-i-debug-my-user-data11:51
holmanbSuperLag: and if you want to run ln 19 the way I did (on a system without cloud-init installed) you could `git clone git@github.com:canonical/cloud-init.git && cd cloud-init` before running that command.11:55
SuperLagholmanb: you still around?16:46
holmanbSuperLag: yes16:50
SuperLagI went to the second link. And there's a python script there. Ran it, it says "userdata.yaml - ok".16:52
holmanbSuperLag: ahh the validate-yaml.py one?16:53
SuperLagbut when I installed cloud-init on my jump box, and was testing... I did "cloud-init schema -c userdata.yaml" and got --> Error: Cloud config schema errors: users.0: {'default': None} is not valid under any of the given schemas16:53
SuperLagso I'm not sure which one to believe :D16:53
SuperLagholmanb: yep16:53
holmanbdon't trust that one16:53
holmanbthanks for pointing that out, the docs need to be updated16:53
SuperLagdon't trust that script? or the latter?16:53
holmanball that validate-yaml.py does is check if your config file is valid yaml16:54
SuperLagwhich isn't sufficient for it to work with cloud-init, I take it?16:54
holmanbcorrect, valid yaml doesn't mean it is valid user-data16:55
holmanbdo you have a colon after "default" in your users list>?16:56
SuperLagI do.16:57
holmanbSuperLag: if you see the paste from before, you'll note that I deleted the colon in the version of your userdata that passed the validation16:57
SuperLagsure enough :D16:57
SuperLagand after removing that it passes muster :D16:58
holmanbSuperLag: \o/16:58
SuperLagIs cloud-init supposed to work the same for all distros? or are there differences depending on distro?16:59
holmanbSuperLag: there are many things that cloud-init can't guarantee across distros - package name, for example, varies from distro to distro17:00
holmanbSuperLag: and there are some distros which cloud-init doesn't support17:00
holmanbSuperLag: however, it operates similarly for most distros17:02
holmanbSuperLag: on the modules page you'll note that each module has a "Supported distros" list17:03
SuperLagOne of the things I haven't tried yet, is to mark one of the generated VMs as a template, and see if subsequent VMs have the cloud-init stuff baked in. Having the VMware datasource makes life VERY nice.17:03
holmanbSuperLag: Should work, depending on what you mean by that.17:07
holmanbSuperLag: You'll note that Module Frequency for many modules is "once-per-instance", so cloud-init will execute those modules only once per instance (this is customizable in cloud.cfg).17:08
andrew76Recently I've noticed problematic behavior using cloud-init's "packages" functionality to install some apt packages on Ubuntu 20.04. It seems to install the packages fine, but then if I look after the fact, the packages contain no files at all17:52
andrew76if I run "dpkg -L <package>", I get "Package '<package>' does not contain any files (!)"; so the apt package is installed, but there are no files associated with it; any suggestions on how to fix this? Thanks!17:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!