Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verifying component health always fails with non-default --apiserver-port #4057

Closed
moduspwnens opened this issue Apr 4, 2019 · 2 comments
Closed
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@moduspwnens
Copy link
Contributor

System: macOS 10.14.4
minikube version: 1.0.0
Command: minikube start --apiserver-port=6443

When I do this, it always fails in the "Verifying component health" stage. However, kubectl works as expected and the cluster seems to be in good health.

I'm not super familiar with golang, but it appears that the function being called to verify the apiserver's health is here:

st, err := bs.GetAPIServerStatus(net.ParseIP(ip))

It's calling a "GetAPIServerStatus" method and passing in only the IP address of the apiserver. The function itself is here:

url := fmt.Sprintf("https://%s:%d/healthz", ip, util.APIServerPort)

And for the port to use, it looks like it may be referencing a constant declared here as 8443:

APIServerPort = 8443

Presumably it should only reference the constant if the user didn't specify the API server port. Although again, my experience with golang is small.

@moduspwnens
Copy link
Contributor Author

$ minikube start --apiserver-port=6443
😄 minikube v1.0.0 on darwin (amd64)
🤹 Downloading Kubernetes v1.14.0 images in the background ...
🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
📶 "minikube" IP address is 192.168.99.165
🐳 Configuring Docker as the container runtime ...
🐳 Version of container runtime is 18.06.2-ce
⌛ Waiting for image downloads to complete ...
✨ Preparing Kubernetes environment ...
🚜 Pulling images required by Kubernetes v1.14.0 ...
🚀 Launching Kubernetes v1.14.0 using kubeadm ...
⌛ Waiting for pods: apiserver proxy etcd scheduler controller dns
🔑 Configuring cluster permissions ...
🤔 Verifying component health ..................................
💣 apiserver checks failed: Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=
Temporary Error: apiserver status=Stopped err=

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new
❌ Problems detected in "kube-addon-manager":
error: WRN: == Error getting default service account, runable to recognize "STDIN": Get https://loetry in 0.5 second ==c
error: unable to reWRN: == Errocognize "STr getting defDIN": Get https://locaault serviclhost:8443/api?timeout=32e account, rs: dial tcp etry in 0.5 second ==
error: unable to recognize "STDIN": Get https://localhost:8443/api?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused

@tstromberg
Copy link
Contributor

Sorry to hear about this, but good catch! We'll definitely want to add --apiserver-port to our integration tests to make sure this doesn't break again in the future.

Help wanted!

@tstromberg tstromberg added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants