[10:06] <pester> smoser: hi, are you here ?
[10:07] <pester> regarding this - https://bugs.launchpad.net/cloud-init/+bug/1712851
[10:07] <pester> I`m currently have this environment and can do tests if anyone interested in debugging this
[16:20] <smoser> blackboxsw, _maybe_remove_legacy_eth0
[16:47] <blackboxsw> larsks: tests/unittests/test_handler/test_schema.py
[18:05] <smoser> powersj, https://code.launchpad.net/~rjschwei/cloud-init/+git/cloud-init/+merge/329616
[18:05] <smoser> why didn't ci bot run on that ?
[18:05] <powersj> I do not know, looking atm
[18:05] <powersj> smoser: ^
[18:10] <powersj> "DEBUG: Users "rjschwei" not allowed to trigger jobs"
[18:10] <powersj> I need to add him to the white list, but I thought anyone who has signed the CLA was on it.
[18:13] <powersj> I can't get onto the VPN right now, keeps timing out, so I can launch it manually
[18:16] <smoser> powersj, he's not signed the cla himself. suse has
[18:17] <smoser> so that would be it.
[18:17] <powersj> ahh! ok at least we can explain it
[21:55] <smoser> rharper, https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/329122
[21:55] <smoser> 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] <smoser> nevermind. i'll update that to mention that logging did not get a timezone.
[22:19] <smoser> blackboxsw, https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/329620
[22:19] <smoser> can you review that ? did that look fine to you ?
[22:50] <blackboxsw> 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)