/srv/irclogs.ubuntu.com/2021/11/01/#cloud-init.txt

holmanbgschanuel: I have never tried what you're talking about, but the cloud-init vmware datasource docs talk about setting the encoding type for userdata/metadata. I don't see that in the commands you linked above.02:33
holmanbgschanuel: https://cloudinit.readthedocs.io/en/latest/topics/datasources/vmware.html?highlight=.encoding02:34
Orpheus[m]New to cloud-init here. How can I "validate" a configuration file without booting a new instance for it?02:46
Orpheus[m]found my answer :)02:56
Orpheus[m]`cloud-init devel schema --config-file file` 02:56
=== IchabodCrane is now known as WrathOfAchilles
juliankI just filed https://bugs.launchpad.net/cloud-init/+bug/194937114:45
ubottuLaunchpad bug 1949371 in cloud-init "'Unable to find a system nic' if openstack lists down ports in json config" [Undecided, New]14:45
juliankThis is currently breaking most of ppc64el scalingstack cloud14:46
juliankArguably the cloud might be broken too14:46
juliankI'm trying to hack an image together that does not error out here, but it's hard14:46
juliankAs I first need to get a server booted14:46
blackboxswThanks juliank: I think we'd need to see what network_data.json is representing to the instance. As the network JSON there will instruct cloud-init what to do with all interfaces. Since OpenStackLocal datasource reads networkdata using the link-local address http://169.254.169.254/openstack/2018-08-27/network_data.json that data should be available to us into the system via console or ssh.17:24
blackboxswOne way we might do that is using write_files: to emit /etc/netplan/50-cloud-init.yaml for only the known NIC you expect to be up  and re-run netplan apply via something like this https://pastebin.canonical.com/p/Jx3cQVDgs7/  17:25
blackboxswthen you can ssh into the instance I hope and `cloud-init query ds.network_json` to see what openstack told us17:26
blackboxswalternative would be to try logging into the console via the novnc url (which I think you said was unavailable on this openstack deployment) openstack console url show <yourinstance>. on my stack I've got the ability to launch a browser to the URL provided to login without SSH17:27
blackboxswlooks like the internet broke CI again. I see it on brett's and my failing PRs https://github.com/canonical/cloud-init/pull/1090/checks?check_run_id=407015885117:48
ubottuPull 1090 in canonical/cloud-init "Add LXD to datasource list" [Open]17:48
holmanb@blackboxsw - it looks like at least one of the failures can be fixed by cherry picking a test dependency from main18:27
holmanbscratch that, I didn't test well enough locally18:31
blackboxswlooks to me like it may have been a spurious error my next pull is running fine https://app.travis-ci.com/github/canonical/cloud-init/builds/24097220020:09
blackboxswfalcojr: lxd_container integration test and lxd_vm tests have passed on my PR20:14
falcojrblackboxsw: https://github.com/canonical/cloud-init/pull/1040 merged!20:43
ubottuPull 1040 in canonical/cloud-init "Add LXD datasource" [Merged]20:43
blackboxswwoo hoo! coffee break. 20:43
falcojrblackboxsw: upstream release PR when ready https://github.com/canonical/cloud-init/pull/109121:24
ubottuPull 1091 in canonical/cloud-init "Release 21.4" [Open]21:24
blackboxswfalcojr: grabbing it now22:46
blackboxswfalcojr: approved the PR, but integration tests have yet to run on 21.4 yet now that LXD datasource is committed. I want to get a +1 from the daily integration runs @ https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd_container-impish-daily/  and https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd_vm-impish-daily/  before we sign and push the upstream version23:12

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