[15:38] <danMS> @blackboxsw - did you or the team got a chance to check out https://bugs.launchpad.net/cloud-init/+bug/1779207 ?
[15:39] <blackboxsw> danMS: didn't quite yet. but it's on my radar for today. (was working on the azure-write-network-each-boot branch yesterday
[15:39] <danMS> ah great - thanks!
[15:41] <blackboxsw> thanks for the ping. danMS can you attach full cloud-init logs to the bug (you can grab them running "sudo cloud-init collect-logs" on the commandline if cloud-init is >= 17.2
[15:42] <danMS> will do
[15:42] <blackboxsw> thank you
[16:11] <blackboxsw> +1 on bug response https://bugs.launchpad.net/cloud-init/+bug/1779847 rharper . yeah I had just finished that validation too :/
[16:12] <blackboxsw> was going to grab tip to be certain.
[16:12] <rharper> blackboxsw: well, nightly build failed
[16:13] <rharper> but what's currently in the repo seems fine
[16:13] <rharper> https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/build/773236/
[16:13] <rharper> haven't looked at it yet
[16:13] <blackboxsw> yeah I had run against 18.2.4 in el-testing
[16:14] <blackboxsw> 18.2.5 rather
[16:14] <rharper> ould not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=epel-7&arch=x86_64 error was
[16:14] <rharper> 14: HTTP Error 503 - Service Unavailable
[16:14] <rharper> not a cloud-init problem, infra problem
[16:14] <rharper> blackboxsw: yeah; they mentioned daily
[16:17] <blackboxsw> yeah just also validated the recent get_linux_distro() logic in cloud-init and added a comment there
[16:17] <blackboxsw> python -c 'from cloudinit.util import get_linux_distro; print(get_linux_distro())'
[16:17] <blackboxsw> ('centos', '7', 'x86_64')
[16:18] <blackboxsw> something smells funky with that bug
[16:18] <blackboxsw> anyway. on to other things