[10:06] smoser: hi, are you here ? [10:07] regarding this - https://bugs.launchpad.net/cloud-init/+bug/1712851 [10:07] Ubuntu bug 1712851 in ironic-python-agent "cloudinit can`t mount configdrive partition" [Undecided,New] [10:07] I`m currently have this environment and can do tests if anyone interested in debugging this [16:20] blackboxsw, _maybe_remove_legacy_eth0 [16:47] larsks: tests/unittests/test_handler/test_schema.py [18:05] powersj, https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/329616 [18:05] why didn't ci bot run on that ? [18:05] I do not know, looking atm [18:05] smoser: ^ [18:10] "DEBUG: Users "rjschwei" not allowed to trigger jobs" [18:10] I need to add him to the white list, but I thought anyone who has signed the CLA was on it. [18:13] I can't get onto the VPN right now, keeps timing out, so I can launch it manually [18:16] powersj, he's not signed the cla himself. suse has [18:17] so that would be it. [18:17] ahh! ok at least we can explain it [21:55] rharper, https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/329122 [21:55] Currently the python logging module will default to a local time which may contain an TZ offset in the values it produces. Switching to UTC time for logging produces consistent values in the cloud-init.log file and avoids issues when the timezone is changed during boot. [21:56] nevermind. i'll update that to mention that logging did not get a timezone. [22:19] blackboxsw, https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/329620 [22:19] can you review that ? did that look fine to you ? [22:50] smoser: yeah this is the branch larsks is working currently to add a unit test around this behavior (but he hit the httppretty issue before pushing the commit)