| === MAbeeTT_ is now known as MAbeeTT | ||
| blackboxsw | falcojr: just approved with doc suggestion https://github.com/canonical/cloud-init/pull/917. Thanks for that take what you think makes sense from that supplement. | 17:10 |
|---|---|---|
| ubottu | Pull 917 in canonical/cloud-init "Use instance-data-sensitive.json in jinja templates (SC-117)" [Open] | 17:10 |
| blackboxsw | yay PR bot links | 17:10 |
| blackboxsw | falcojr: thanks for the doc update. wheee I get some soft-ball reviews in today for credit https://github.com/canonical/cloud-init/pull/918 | 17:12 |
| ubottu | Pull 918 in canonical/cloud-init "doc: Update NoCloud docs stating required files" [Open] | 17:12 |
| ananke | I'm trying to figure out how to kick off running of write-files module, to force it writing files manually, since it's set to per-instance | 18:56 |
| ananke | I've tried 'cloud-init single --name cc_write_files --frequency always', but I get the following error in log files: | 18:57 |
| ananke | udo cloud-init single --name cc_write_files --frequency always | 18:58 |
| ananke | oops, wrong paste | 18:58 |
| ananke | 2021-06-10 18:57:35,470 - helpers.py[DEBUG]: Running config-cc_write_files using lock (<cloudinit.helpers.DummyLock object at 0x7f8ab8465a60>) | 18:58 |
| ananke | 2021-06-10 18:57:35,470 - cc_write_files.py[DEBUG]: Skipping module named cc_write_files, no/empty 'write_files' key in configuration | 18:58 |
| ananke | the docs indicate that this should be the correct module name | 18:59 |
| blackboxsw | ananke: `sudo cloud-init devel schema --system --annotate` beware if you have username's passwords in that userdata before pasteing | 19:00 |
| blackboxsw | it'll print out the full userdata provided to the vm and allow us to check for syntax errors or missing keys | 19:00 |
| ananke | unrecognized argument: --system | 19:01 |
| blackboxsw | oops too new a feature: cloud-init --version | 19:01 |
| blackboxsw | ananke: `sudo cloud-init query userdata` does the same without error format annotations | 19:02 |
| blackboxsw | but depends on whether your vm has new enough cloud-init too :) | 19:02 |
| ananke | ahh, you are right on the money that the syntax may be the culprit. I've removed the additional items I added to write-files, and it works | 19:03 |
| blackboxsw | +1 yeah something is invalid YAML in that output | 19:03 |
| blackboxsw | +1 yeah something is invalid YAML in that userdata | 19:03 |
| ananke | it's cloud-init v 20.2 | 19:03 |
| ananke | thank you, this gives me enough info to go on. the original error just threw me off track | 19:04 |
| blackboxsw | ananke: for quick iterations on your cloud-init env w/ 20.2: sudo cloud-init query userdata > ud.yaml; cloud-init devel schema --config-file --annotate ud.yaml; | 19:06 |
| blackboxsw | then you don't have to boot/reboot instances as you keep changing ud.yaml. | 19:06 |
| blackboxsw | at some point it'll work :) | 19:07 |
| blackboxsw | +1 | 19:07 |
| ananke | cheers! | 19:12 |
| blackboxsw | falcojr: do you know if you plan to get to merging https://github.com/canonical/pycloudlib/pull/148 today. I think it might give us slight CI speed improvement on UA | 19:18 |
| ubottu | Pull 148 in canonical/pycloudlib "Move SSH retry logic to boot wait method (SC-58)" [Open] | 19:18 |
| falcojr | yes, sorry, I'll do that now | 19:19 |
| blackboxsw | excellent | 19:20 |
| blackboxsw | I realize logically doesn't make sense for me to ask/press as it took me so long to review :) | 19:20 |
| falcojr | pushed my squashes, once CI finishes I'll merge it | 19:23 |
| falcojr | blackboxsw: done! | 19:43 |
| blackboxsw | Thanks falcojr | 19:44 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!