API errors cause "Non compatible" messages in the logs
Summary
Log tells me my up-to-date gitlab-ci-runner is incompatible, because the GitLab API was timing out
Steps to reproduce
- Wait for GitLab API to time out (during upgrade, or normally)
- Look in your logs for the CI runner
How one can reproduce the issue - this is very important Null route gitlab.com from a CI runner
Actual behavior
2017-05-01T14:43:28.290653646Z WARNING: Checking for jobs... failed runner=791a8779 status=couldn't execute POST against https://gitlab.com/api/v4/jobs/request: Post https://gitlab.com/api/v4/jobs/request: dial tcp: i/o timeout
2017-05-01T14:43:58.293316512Z ERROR: Checking GitLab compatibility... not-compatible reason=GitLab Runner >= 9.0 can be used ONLY with GitLab CE/EE >= 9.0 result=-1 runner=791a8779 statusText=couldn't execute POST against https://gitlab.com/api/v4/runners/verify: Post https://gitlab.com/api/v4/runners/verify: dial tcp: i/o timeout
2017-05-01T14:44:28.302103952Z WARNING: Checking for jobs... failed runner=791a8779 status=couldn't execute POST against https://gitlab.com/api/v4/jobs/request: Post https://gitlab.com/api/v4/jobs/request: dial tcp: i/o timeout
2017-05-01T14:44:58.30340973Z ERROR: Checking GitLab compatibility... not-compatible reason=GitLab Runner >= 9.0 can be used ONLY with GitLab CE/EE >= 9.0 result=-1 runner=791a8779 statusText=couldn't execute POST against https://gitlab.com/api/v4/runners/verify: Post https://gitlab.com/api/v4/runners/verify: dial tcp: i/o timeout
2017-05-01T14:45:28.310565573Z WARNING: Checking for jobs... failed runner=791a8779 status=couldn't execute POST against https://gitlab.com/api/v4/jobs/request: Post https://gitlab.com/api/v4/jobs/request: dial tcp: i/o timeout
2017-05-01T14:45:58.312627238Z ERROR: Checking GitLab compatibility... not-compatible reason=GitLab Runner >= 9.0 can be used ONLY with GitLab CE/EE >= 9.0 result=-1 runner=791a8779 statusText=couldn't execute POST against https://gitlab.com/api/v4/runners/verify: Post https://gitlab.com/api/v4/runners/verify: dial tcp: lookup gitlab.com on 10.3.0.10:53: dial udp 10.3.0.10:53: i/o timeout
2017-05-01T14:46:28.318705873Z WARNING: Checking for jobs... failed runner=791a8779 status=couldn't execute POST against https://gitlab.com/api/v4/jobs/request: Post https://gitlab.com/api/v4/jobs/request: dial tcp: i/o timeout
2017-05-01T14:46:58.320846278Z ERROR: Checking GitLab compatibility... not-compatible reason=GitLab Runner >= 9.0 can be used ONLY with GitLab CE/EE >= 9.0 result=-1 runner=791a8779 statusText=couldn't execute POST against https://gitlab.com/api/v4/runners/verify: Post https://gitlab.com/api/v4/runners/verify: dial tcp: i/o timeout
What actually happens
A message that my client is incompatible
Expected behavior
An error reflecting the timeout to the API and to please be patient
What you should see instead
A log saying that the GitLab API is not responding and to check your connectivity or status.gitlab.com
Relevant logs and/or screenshots
See above
Environment description
Private runners pointing at gitlab.com
The executor doesn't matter.
Used GitLab Runner version
9.1.x, running from a container, so "latest".