minishift: Improve Error Message when GitHub Rate Limiting hits

General information

Minishift version: minishift v1.29.0+72fa7b2
OS: Linux / macOS / Windows: Fedora release 29 (Twenty Nine)
Hypervisor: KVM / xhyve / Hyper-V / VirtualBox: KVM /usr/local/bin/docker-machine-driver-kvm

Steps to reproduce

Start Minishift : $ minishift start --memory=8GB
If unauthenticated requests at the time of start have maxed out the rate limiting for GitHub, observe the error message:

Hit github rate limit: GET https://api.github.com/repos/openshift/origin/releases/tags/v3.11.0: 403 API rate limit exceeded for 125.16.100.118. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) [rate reset in 27m30s]
FAIL

I happened to be sitting in a room with a bunch 'o wonderful DevTools engineers who knew how to handle this. For one, we can disable the check:

$ minishift config set skip-check-openshift-release true

I also got to Googlin’ and saw in #3090 that there’s an environment variable one may set to make an authenticated request:

MINISHIFT_GITHUB_API_TOKEN

How about reflecting those options in the error message so users know what to do next?

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 4
Comments: 16 (10 by maintainers)

Most upvoted comments

I just hit this, and cannot create a new minishift VM (after having to delete my old one). The image is still cached from earlier, so failing start because we can’t check the image adds somewhat needless frustration.

For my use case, minishift config set skip-check-openshift-release true solves the problem.

amisevsk on Jan 11, 2019