[03:24] https://unix.stackexchange.com/questions/692871/cloud-init-log-shows-write-files-0-additional-properties-are-not-allowed-defe [03:24] anyone have a chance to look at that? === Guest88 is now known as Guest8897 [10:26] Continuing my investigation from yesterday, it seems the cloud-init just ignores my `userdata`, even if I `cloud-init clean` and `cloud-init init` [10:28] I've managed to get an error out of `cloud-init devel --system --annotate` but it just complains that I'm not using the `#cloud-config` syntax. I'm using the classic bash shebang, which works on AWS linux, but not, it seems, on this custom AMI based on Ubuntu 18.04 [10:28] more testing to follow [10:28] help would be greatly appreciated [13:20] Guest8897: I think more information is required to help debug. Could you share the userdata you're trying to run and cloud-init logs? [13:39] EvanCarroll: looking [14:24] EvanCarroll: Thanks for dropping the SO link here. I responded on SO with a response and some context. [14:55] holmanb: Thanks a ton for your answers there. I was thinking it was a bug in cloud-init itself, and was digging around never even considering that the code that generated the error isn't there anymore. [14:57] EvanCarroll: No problem, happy to help. [20:35] is there a best practice how to properly deal with locales? I generated /etc/locale.gen with the proper content and have »locale: 'C.UTF-8'« in my userdata. but 'locale' still says »locale: Cannot set LC_CTYPE to default locale: No such file or directory« because 'locale-gen' has not been run AFAIU. [22:42] http://ix.io/3SHR cloud-init does not run locale-gen with this config because the specified locale already exists. that’s unfortunate. I have to use a 'runcmd' to run 'locale-gen'. IMHO this could/should be improved to compare 'locale -a' with /etc/locale.gen and run 'locale-gen' if there are any locales missing. [23:56] henk: I think the assumption in cloud-init's locale module is that the distro-provided locales should work without generating new ones.