[12:44] <jchittum> maybe an odd question, but is there some "simple" thing i can add to cloud-init user-data that will _definitely_ cause cloud-init to fail and report an error?
[13:15] <minimal> jchittum: when you say "fail and report an error" exactly what do you mean? If your user-data includes some incorrect setting values then you will get schema error messages both in the cloud-init.log and on the console. What type of failure are you wanting?
[13:20] <cjp256> holmanb: https://github.com/canonical/cloud-init/pull/2091
[13:20] -ubottu:#cloud-init- Pull 2091 in canonical/cloud-init "unittests/sources: patch util.get_cmdline() for datasource tests" [Open]
[13:25] <jchittum> pretty much anything that will do `cloud-init status : error` and have `cloud-init status --format json` have things in `{errors:[]}`, in a reliable fashion.
[13:26] <jchittum> i'm working on better Ubuntu cloud-image integration tests (the tests run on images, not cloud-init), and want to make sure I am suitably capturing the errors so i can bubble them up in our tests
[13:39] <holmanb> cjp256: Thanks!
[13:39] <cjp256> added another one for vmware but unrelated to the other change
[13:41] <cjp256> didn't figure out why that one works otherwise https://github.com/canonical/cloud-init/pull/2092
[13:41] -ubottu:#cloud-init- Pull 2092 in canonical/cloud-init "tests/vmware: fix test_no_data_access_method failure" [Open]
[13:42] <jchittum> i think i have a reliable thing for me to test our error handling and bubbling up. i since i know `resize2fs` is unhappy in lunar, ran lunar and a runcmd that's `resize2fs` over and over again 🤣
[13:46] <aciba[m]> jchittum: invalid/deprecated user-data is not treated as a hard error (to keep backwards compatibility), and it is not included in the output of cloud-init status (I think). one can manually run cloud-init schema --system to check it
[22:04] <holmanb> rfc related to command line parsing and nocloud: https://github.com/canonical/cloud-init/pull/2093
[22:04] -ubottu:#cloud-init- Pull 2093 in canonical/cloud-init "Standardize NoCloud Command Line Parsing" [Open]
[23:03] <blackboxsw> two fun PRS for desktop live installer to make desktop environments execute cloud-init.service after NetworkManager: https://code.launchpad.net/~chad.smith/livecd-rootfs/+git/livecd-rootfs/+merge/439585  https://code.launchpad.net/~chad.smith/livecd-rootfs/+git/livecd-rootfs/+merge/439586
[23:04] <blackboxsw> our desktop installer live iso needs to order after NetworkManager.service so any autoinstall nocloud directives can properly resolve FQDNs which could be provided on the kernel cmdline