| === esv_ is now known as esv | |
| === Guest1951 is now known as Daniel | |
| [10:45] <itjamie> @meena / @minimal I've refactored https://github.com/canonical/cloud-init/pull/1808/files. is that closer to what you'd like to see? | |
| === djhankb4 is now known as djhankb | |
| [15:23] <meena> itjamie: what happens if that replacement fails? it returns None, from what i can see. | |
| [15:25] <meena> you need another if not seedfrom: | |
| [16:06] * meena wonders if anyone has survived last week's in person meet and can now review my PRs | |
| [16:20] <meena> falcojr: ping | |
| [16:21] <falcojr> lol, I'll get to it today | |
| [16:21] <falcojr> though...I may be the only one...others on the team came back with colds | |
| [16:23] <meena> brrrr | |
| [16:24] <meena> falcojr: to reiterate from last week: 20:24 <meena> falcojr: might be good to rework my schedule next week with all of y'all's schedule in mind /cc jrm | |
| [16:25] <minimal> BTW I just spend a couple of days debugging an issue where c-i fails on all 4 init.d services thinking it was "ubuntu" when it was running on Alpine - seems if the /etc/cloud/cloud.cfg is not valid YAML this happens but it doesn't log that the file is invalid. Doh! | |
| [16:27] <falcojr> minimal: ooph, I think part of it may be due to us using the cloud.cfg to setup logging. Feel free to file a bug though so we can look a little deeper | |
| === djhankb3 is now known as djhankb | |
| [16:30] <minimal> falcojr: it did create logs, I jsut ended up adding print statements to stages.py and some other files to try and understand what was going on and spotting the self config being used didn't match the cloud.cfg contents | |
| [16:46] <rjt> Is there a built-in command to verify the configuration files? Checks the Line ending format. ByteOrderMark. YAML syntax. Checks that the architecture matches. | |
| [16:55] <minimal> rjt: I just used yamllint | |
| [17:00] <meena> which endianness does YAML have? | |
| [17:05] <meena> (that's a joke question, btw) | |
| [17:06] <waldi> it can be both. yaml is supposed to support utf-16 | |
| [17:06] <waldi> (i would assume most parsers do not) | |
| [17:07] <minimal> which version of yaml is being talked about? ;-) | |
| [17:07] <minimal> c-i is YAML 1.1 from memory | |
| [17:10] <waldi> minimal: https://yaml.org/spec/1.1/#id868742 | |
| [17:18] <meena> i need to sit down and review https://github.com/canonical/cloud-init/pull/1756 before it gets merged | |
| [17:18] -ubottu:#cloud-init- Pull 1756 in canonical/cloud-init "Feature: Kernel Modules" [Open] | |
| [17:56] <rjt> Thanks for the link. "If a character stream does not begin with a byte order mark (#FEFF), the character encoding shall be UTF-8. " | |
| [17:57] <rjt> Did not know JSON cannot have a BOM at all. Thinking it must always be network byte order or something like that. Endianness confuses the heck out of me. | |
| [20:17] <meena> falcojr: thank you so much | |
| === VoliKoN1 is now known as VoliKoN | |
| === VoliKoN1 is now known as VoliKoN | |
| === VoliKoN4 is now known as VoliKoN | |