Closed xkrogen closed 6 years ago
Travis CI passes again, and I tested this on our internal cluster as well. It looks like it fixes the issue.
I'm not totally sure what happened, but I suspect something changed in the Travis CI infrastructure such that the host name resolved differently, in a way that made the previous version no longer work properly.
Can't reproduce this locally, so submitting a patch to get a Travis CI run...