[13:50] <Odd_Bloke> BugzBunny: /var/log/cloud-init-output.log should contain the output from those processes, that would be helpful for debugging.
[15:51] <paride> smoser, o/ In the end I'm thinking to approve https://github.com/canonical/cloud-utils/pull/28 as-is for the moment, and open a separate low-priority bug about converting `LANG=C sfdisk ...` to `sfdisk --dump`. Newer versions of sfdisk do show the sector-size in --dump, so it would work for us here, but break compatibility with older versions of
[15:51] <paride> sfdisk
[15:52] <paride> and it may be reasonable to just fix the bug for the moment, setting LANG=C as done elsewhere in the same repo
[15:53] <paride> (yes I'm retracing my steps here)
[15:59] <smoser> I agree with the fix there. LANG=C should be used anywhere you are parsing output of something.
[16:03] <paride> ty scott
[16:18] <BugzBunny> Odd_Bloke: I actually included it in the pastebin above, in my testing, apparently there's a 20 second delay between network configuration is applied and an active network connection. And I can't seem to find any informaiton regarding putting a pause or sleep in cloud-init. Here's a post describing the problem here https://l.lhputils.info/3H1KN
[16:22] <Odd_Bloke> BugzBunny: I see cloud-init.log, but not cloud-init-output.log?
[16:30] <BugzBunny> Ahh, I didn't know there was a difference, unfortunately there isn't one.
[16:31] <BugzBunny> Is that something that should be enabled in cloud.cfg?
[16:32] <BugzBunny> Just to clarify, that log would be in /var/log/cloud-init-output.log ?
[16:33] <smoser> BugzBunny:you're on centos 7 ?
[16:33] <smoser> it is default just about everywhere
[16:34] <BugzBunny> Yes, although I like to point that this is a LXD container image using their https://github.com/lxc/distrobuilder
[16:36] <smoser> put this into /etc/cloud/cloud.cfg.d/log.cfg
[16:36] <smoser>  output: {all: '| tee -a /var/log/cloud-init-output.log'}
[16:41] <BugzBunny> Alright, I have to circle back to you on this. I would have to erase and create a new container, create the configuration, run a 'cloud-init clean', and reboot to reproduce.
[17:25] <Odd_Bloke> BugzBunny: If you run `cloud-init collect-logs`, that generates a tarball with a bunch of debugging info; that'll include most of what we need.
[17:29] <smoser> Odd_Bloke: id ont think that is there . i think default logging to -output came before cloud-init collect-logs
[17:29] <smoser> cent7 is *really* old
[18:21] <Odd_Bloke> smoser: The log says 19.4, which I think should include it?  I guess we'll find out! :p
[18:27] <smoser> oh. but i would have thought that would have cloud-init-output.log too t hen.
[20:49] <Odd_Bloke> Yeah, if I had to guess, the Python code could have been updated in the package without the new configuration files from upstream?