template: Try to poke the GCP auth endpoint in the container #5720
Conversation
openshift-ci-robot
added
size/XS
openshift-ci-robot
added
size/S
Working on the theory that there is some sort of DNS / initial connection problem when talking to the GCP auth endpoint from inside the test pod on GCP, try to poke the auth endpoint before we continue.
openshift-ci-robot
added
size/XS
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@smarterclayton: Updated the following 2 configmaps:
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@smarterclayton: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
…e: Error-catching for Google OAuth pokes Catch non-zero exit codes in the poke that initially landed in 0ec2cd9 (template: Try to poke the GCP auth endpoint in the container, 2019-10-31, openshift#5720) to make it easier to rule out that code when debugging mysterious failures like [1]: Container setup exited with code 6, reason Error --- Lease acquired, installing... Installing from release registry.svc.ci.openshift.org/ci-op-r6dy480t/release@sha256:284ff92845dbfc3ca1be73159acc58b36cbfe03aed05d0f79582ea4207035da9 --- From curl(1), exit 6 is: Couldn't resolve host. The given remote host was not resolved. Clayton suggested including the exit code in the non-zero exit log entry [2]. Testing locally: $ echo $BASH_VERSION 4.2.46(2)-release $ code="$( curl -s -o /dev/null -w "%{http_code}" https://does-not-exist.example.com -X POST -d '' || echo "Failed to POST https://oauth2.googleapis.com/token with $?" 1>&2)" Failed to POST https://oauth2.googleapis.com/token with 6 [1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_installer/2724/pull-ci-openshift-installer-release-4.3-e2e-gcp/8 [2]: openshift#6190 (comment)
3 participants
Working on the theory that there is some sort of DNS / initial
connection problem when talking to the GCP auth endpoint from
inside the test pod on GCP, try to poke the auth endpoint before
we continue.
Will fail with a clean message if we can't hit the accounts endpoint.