Fallback to IPv4 pool to fix keyserver receive failed in Travis CI builds #464
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Travis CI builds were failing, seemingly at random in azavea/docker-django#56. After further investigation, it turned out this was happening because IPv6 networking for Docker is disabled by default, and the SKS Keyservers high-availability pool contains some IPv6-only servers:
While working on docker-django, I referenced the Travis CI builds for this repository, and saw that many of them were failing as well.
This PR adds a conditional expression to fallback to the IPv4-only SKS pool if we get an IPv6 server from the high-availability pool.
Testing
See Travis CI build: https://travis-ci.com/rbreslow/postgres/builds/78322372
https://travis-ci.com/rbreslow/postgres/jobs/133223806: