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

minikube addons enable logviewer #10857

Closed
husseinferas opened this issue Mar 17, 2021 · 4 comments
Closed

minikube addons enable logviewer #10857

husseinferas opened this issue Mar 17, 2021 · 4 comments
Labels
area/addons kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@husseinferas
Copy link

❌ Exiting due to MK_ENABLE: run callbacks: running callbacks: [sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml: Process exited with status 1
stdout:
service/logviewer unchanged
serviceaccount/sa-logviewer unchanged
clusterrole.rbac.authorization.k8s.io/cr-logviewer unchanged
clusterrolebinding.rbac.authorization.k8s.io/crb-logviewer unchanged

stderr:
error: error parsing /etc/kubernetes/addons/logviewer-dp-and-svc.yaml: error converting YAML to JSON: yaml: line 25: did not find expected key
]

@spowelljr spowelljr added area/addons kind/support Categorizes issue or PR as a support question. labels Mar 17, 2021
@spowelljr
Copy link
Member

Thank you for sharing your experience! If you don't mind, could you please provide:

  • The version of minikube.
  • The driver you are using. (docker, virtualbox, hyperv....)
  • The Operation system you are using (windows, mac or linux and version of it)
  • The full output of the command you are using by adding --alsologtostderr, for example:
$ minikube start --alsologtostderr

This will help us isolate the problem further. Thank you!

/triage needs-information

@k8s-ci-robot k8s-ci-robot added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 17, 2021
@husseinferas
Copy link
Author

Thank you for reply @spowelljr

  • The version of minikube. v1.15.1
  • The driver you are using. (docker, virtualbox, hyperv....) docker
  • The Operation system you are using (windows, mac or linux and version of it) linux ubunut 20 desktop
  • The full output of the command you are using by adding --alsologtostderr, for example:

` I0318 08:45:10.371538 23734 out.go:185] Setting OutFile to fd 1 ...
I0318 08:45:10.372237 23734 out.go:237] isatty.IsTerminal(1) = true
I0318 08:45:10.372248 23734 out.go:198] Setting ErrFile to fd 2...
I0318 08:45:10.372257 23734 out.go:237] isatty.IsTerminal(2) = true
I0318 08:45:10.372355 23734 root.go:279] Updating PATH: /home/hussein/.minikube/bin
I0318 08:45:10.372806 23734 addons.go:55] Setting logviewer=true in profile "minikube"
I0318 08:45:10.372854 23734 addons.go:131] Setting addon logviewer=true in "minikube"
I0318 08:45:10.372878 23734 host.go:66] Checking if "minikube" exists ...
I0318 08:45:10.373637 23734 cli_runner.go:110] Run: docker container inspect minikube --format={{.State.Status}}
I0318 08:45:10.408819 23734 addons.go:243] installing /etc/kubernetes/addons/logviewer-dp-and-svc.yaml
I0318 08:45:10.408857 23734 ssh_runner.go:215] scp deploy/addons/logviewer/logviewer-dp-and-svc.yaml.tmpl --> /etc/kubernetes/addons/logviewer-dp-and-svc.yaml (1973 bytes)
I0318 08:45:10.408923 23734 cli_runner.go:110] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube
I0318 08:45:10.443904 23734 sshutil.go:45] new ssh client: &{IP:127.0.0.1 Port:49156 SSHKeyPath:/home/hussein/.minikube/machines/minikube/id_rsa Username:docker}
I0318 08:45:10.557026 23734 addons.go:243] installing /etc/kubernetes/addons/logviewer-rbac.yaml
I0318 08:45:10.557050 23734 ssh_runner.go:215] scp deploy/addons/logviewer/logviewer-rbac.yaml.tmpl --> /etc/kubernetes/addons/logviewer-rbac.yaml (1064 bytes)
I0318 08:45:10.567968 23734 ssh_runner.go:148] Run: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml
W0318 08:45:10.711808 23734 addons.go:264] apply failed, will retry: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml: Process exited with status 1
stdout:
service/logviewer unchanged
serviceaccount/sa-logviewer unchanged
clusterrole.rbac.authorization.k8s.io/cr-logviewer unchanged
clusterrolebinding.rbac.authorization.k8s.io/crb-logviewer unchanged

stderr:
error: error parsing /etc/kubernetes/addons/logviewer-dp-and-svc.yaml: error converting YAML to JSON: yaml: line 25: did not find expected key
I0318 08:45:10.712075 23734 retry.go:31] will retry after 276.165072ms: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml: Process exited with status 1
stdout:
service/logviewer unchanged
serviceaccount/sa-logviewer unchanged
clusterrole.rbac.authorization.k8s.io/cr-logviewer unchanged
clusterrolebinding.rbac.authorization.k8s.io/crb-logviewer unchanged

stderr:
error: error parsing /etc/kubernetes/addons/logviewer-dp-and-svc.yaml: error converting YAML to JSON: yaml: line 25: did not find expected key
I0318 08:45:10.988487 23734 ssh_runner.go:148] Run: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml
W0318 08:45:11.141522 23734 addons.go:264] apply failed, will retry: sudo KUBECONFIG=/var/lib/minikube/kubeconfig /var/lib/minikube/binaries/v1.19.4/kubectl apply -f /etc/kubernetes/addons/logviewer-dp-and-svc.yaml -f /etc/kubernetes/addons/logviewer-rbac.yaml: Process exited with status 1
stdout:
service/logviewer unchanged
serviceaccount/sa-logviewer unchanged
clusterrole.rbac.authorization.k8s.io/cr-logviewer unchanged
clusterrolebinding.rbac.authorization.k8s.io/crb-logviewer unchanged

`

@spowelljr
Copy link
Member

spowelljr commented Mar 18, 2021

Hi @husseinferas, thank you very much for your response.

I did some digging for your issue, based on the logs you provided me it seems the issue is apply failed, will retry followed by error converting YAML to JSON: yaml: line 25: did not find expected key.

Here's a past issue that seems to have the same problem you're experiencing #9722.

Based on that issue this seems to be an issue specific to v1.15.0 & v1.15.1 of minikube.

Please try updating to the newest version of minikube v1.18.1 and let me know if the error still persists.

@sharifelgamal
Copy link
Collaborator

@husseinferas Did upgrading to minikube 1.18.1 help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/addons kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants