Minikube: Invalid problem detection: "kube-addon-manager": error: no objects passed tpod

[manases13]

Problems detected in "kube-addon-manager":
error: no objects passed tpod/storage-provisioner created
error: noINFO: == Kuberne objects passed to apptes addon ensure ly
error: no objectINFO: == Reconcilings passed to with addoapply

[tstromberg]

Thank you for sharing your experience! I think this particular 'problem detected' prompt is likely a false positive. Do you mind sharing:

• The exact command-lines used so that we can replicate the issue
• The full output of minikube start. From what you have shared so far, I can't tell if minikube is warning against something, or crashing.
• The output of the "minikube logs" command

Thanks!

[waynewyang]

I met the same problem, my version info as below,thanks

waynewyang:api waynewyang$ minikube version
minikube version: v1.0.0

waynewyang:api waynewyang$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-26T00:04:52Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

waynewyang:api waynewyang$ uname -a
Darwin waynewyang.local 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64

waynewyang:api waynewyang$ more /System/Library/CoreServices/SystemVersion.plist

ProductBuildVersion 18E226 ProductCopyright 1983-2019 Apple Inc. ProductName Mac OS X ProductUserVisibleVersion 10.14.4 ProductVersion 10.14.4 iOSSupportVersion 12.2

minikube_start.log

minikube_logs.log

[cixuuz]

I got the same error too.

❯ minikube start --memory 2048 --cpus 2
😄  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.104
🐳  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
💣  Error starting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition

😿  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: no objects passed to apply
    error: no objects passed to apply
    error: no objects passed to apply

❯ minikube version
minikube version: v1.0.0

Logs:
minikube_logs.log

[zackzhangkai]

I have the same problem，but mime more likely is the mirros error；but i have proxy to google

😄 minikube v1.0.0 on darwin (amd64)
🤹 Downloading Kubernetes v1.14.0 images in the background ...
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delet
e' to delete this one.
🏃 Re-using the currently running virtualbox VM for "minikube" ...
⌛ Waiting for SSH access ...
📶 "minikube" IP address is 192.168.99.100
🌐 Found network options:
▪ HTTP_PROXY=http://127.0.0.1:8118
▪ HTTPS_PROXY=http://127.0.0.1:8118
🐳 Configuring Docker as the container runtime ...
▪ env HTTP_PROXY=http://127.0.0.1:8118
▪ env HTTPS_PROXY=http://127.0.0.1:8118
🐳 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 ...
❌ Unable to pull images, which may be OK: running cmd: sudo kubeadm config images
pull --config /var/lib/kubeadm.yaml: command failed: sudo kubeadm config images pu
ll --config /var/lib/kubeadm.yaml
stdout:
stderr: failed to pull image "k8s.gcr.io/kube-apiserver:v1.14.0": output: Error res
ponse from daemon: Get https://k8s.gcr.io/v2/: proxyconnect tcp: dial tcp 127.0.0.1
:8118: connect: connection refused
, error: exit status 1
: Process exited with status 1
🔄 Relaunching Kubernetes v1.14.0 using kubeadm ...
⌛ Waiting for pods: apiserver
💣 Error restarting cluster: wait: waiting for component=kube-apiserver: timed out
waiting for the condition

😿 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: no objects passed to apply
error: no objects passed to apply
error: no objects INFO: == Kubernetes addon ensure completed at 2019-04-09T07:3
4:38+00:00 ==

[thanusivan]

root@k8sm:/usr/local/bin# ./minikube start
 minikube v1.0.0 on linux (amd64)
魯 Downloading Kubernetes v1.14.0 images in the background ...
2019/04/26 21:51:04 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/26 21:51:04 No matching credentials were found, falling back on anonymous
2019/04/26 21:51:04 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/26 21:51:04 No matching credentials were found, falling back on anonymous
2019/04/26 21:51:04 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/26 21:51:04 No matching credentials were found, falling back on anonymous
2019/04/26 21:51:04 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/26 21:51:04 No matching credentials were found, falling back on anonymous
2019/04/26 21:51:04 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no such file or directory
2019/04/26 21:51:04 No matching credentials were found, falling back on anonymous

⚠️ Ignoring --vm-driver=virtualbox, as the existing "minikube" VM was created using the none driver.
⚠️ To switch drivers, you may create a new VM using minikube start -p <name> --vm-driver=virtualbox
⚠️ Alternatively, you may delete the existing VM using minikube delete -p minikube

 Restarting existing none VM for "minikube" ...
⌛ Waiting for SSH access ...
 "minikube" IP address is 192.168.43.238
 Configuring Docker as the container runtime ...
 Version of container runtime is 18.09.2
⌛ Waiting for image downloads to complete ...
✨ Preparing Kubernetes environment ...
 Downloading kubeadm v1.14.0
 Downloading kubelet v1.14.0
 Pulling images required by Kubernetes v1.14.0 ...
 Relaunching Kubernetes v1.14.0 using kubeadm ...
⌛ Waiting for pods: apiserver proxy
 Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

 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: error executing template "{{with index .secrets 0}}{{.name}}{{end}}": template: output:1:7: executing "output" at : error calling index: index of untyped nil
error: no objects passed to apply
error: no objects passed to apply
root@k8sm:/usr/local/bin#

I have same problem.. any solution do you have ?

[edwardstudy]

Hi, Do you guys know how to fix it?

I just used --kubernetes-version v1.13.0 to install lower version

[pendenaor]

I'm using minikube v1.0.1 on windows 10 and virtualbox v6.0.6 and i've almost got the same errors:

>minikube start
o   minikube v1.0.1 on windows (amd64)
$   Downloading Kubernetes v1.14.1 images in the background ...
i   Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
:   Restarting existing virtualbox VM for "minikube" ...
:   Waiting for SSH access ...
-   "minikube" IP address is 192.168.99.100
-   Configuring Docker as the container runtime ...
-   Version of container runtime is 18.06.3-ce
:   Waiting for image downloads to complete ...
-   Preparing Kubernetes environment ...
@   Downloading kubeadm v1.14.1
@   Downloading kubelet v1.14.1
-   Pulling images required by Kubernetes v1.14.1 ...
:   Relaunching Kubernetes v1.14.1 using kubeadm ...
:   Waiting for pods: apiserver proxy
!   Error restarting cluster: wait: waiting for k8s-app=kube-proxy: timed out waiting for the condition

*   Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
-   https://github.com/kubernetes/minikube/issues/new
X   Problems detected in "kube-addon-manager":
    - error: serviceaccount/storno objects passed to apply
    - error: noINFO: Leader is minikube

Update Just delete and start again and the problem is gone!

>minikube delete
x   Deleting "minikube" from virtualbox ...
-   The "minikube" cluster has been deleted.

>minikube start
o   minikube v1.0.1 on windows (amd64)
$   Downloading Kubernetes v1.14.1 images in the background ...
>   Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
-   "minikube" IP address is 192.168.99.101
-   Configuring Docker as the container runtime ...
-   Version of container runtime is 18.06.3-ce
:   Waiting for image downloads to complete ...
-   Preparing Kubernetes environment ...
-   Pulling images required by Kubernetes v1.14.1 ...
-   Launching Kubernetes v1.14.1 using kubeadm ...
:   Waiting for pods: apiserver proxy etcd scheduler controller dns
-   Configuring cluster permissions ...
-   Verifying component health .....
+   kubectl is now configured to use "minikube"
=   Done! Thank you for using minikube!

[mifiguer]

using minikube 1.0.1 on Mac, even minikube delete didn't fix the problem:
$ minikube -v5 start
o minikube v1.0.1 on darwin (amd64)
$ Downloading Kubernetes v1.14.1 images in the background ...

Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
Downloading /Users/mifiguer/.minikube/cache/boot2docker.iso from file:///Users/mifiguer/.minikube/cache/iso/minikube-v1.0.1.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting the VM...
Check network to re-create if needed...
Waiting for an IP...
Setting Docker configuration on the remote daemon...

• "minikube" IP address is 192.168.99.119
• Configuring Docker as the container runtime ...
• Version of container runtime is 18.06.3-ce
  : Waiting for image downloads to complete ...
• Preparing Kubernetes environment ...
• Pulling images required by Kubernetes v1.14.1 ...
• Launching Kubernetes v1.14.1 using kubeadm ...
  : Waiting for pods: apiserver
  ! Error starting cluster: wait: waiting for component=kube-apiserver: timed out waiting for the condition

• Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
• https://github.com/kubernetes/minikube/issues/new
  X Problems detected in "kube-addon-manager":
  
  
  
  • error: no obj.5 second ==
  
  
  • error: no objects INFO: == Kuberpassed to applnetes addon reconcile completed at 2019-05-13T18:07:41+00:00 ==
  
  
  • error: no objects passed INFO: == Kubto apply
  
  

[mariocoloma]

I was getting an error to do with the apiserver when I ran 'minikube start'

Error msg: 'Error restarting cluster: waiting for apiserver: timed out waiting for the condition'

After restarting my system and trying again the error was persistent and minikube kept crashing.

The solution was to delete the cluster and start a new one.

minikube delete
minikube start

[frbimo]

I have the same issue when relaunch minikube:

 ⚡ root@bee  ~  minikube start --vm-driver=none
😄  minikube v1.2.0 on linux (amd64)
💡  Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
🔄  Restarting existing none VM for "minikube" ...
⌛  Waiting for SSH access ...
🐳  Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6
    ▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
🔄  Relaunching Kubernetes v1.15.0 using kubeadm ... 

💣  Error restarting cluster: waiting for apiserver: timed out waiting for the condition

😿  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: unable to recognize "STDIN": Get https://localhost:8443/api?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused
    error: unable to recognize "STDIN": Get https://localhost:8443/api?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused
    error: unable to recognize "STDIN": Get https://localhost:8443/api?timeout=32s: dial tcp 127.0.0.1:8443: connect: connection refused

Have tried:

minikube stop
minikube start --vm-driver=none

At that time my docker service was running.
And i tried "minikube delete" solution and its worked. But i cant use my instances again, so i'm not seeing this solution as best practice.

[mariocoloma]

@frbimo 2 things

1. Did you get it to run before with --vm-driver=none?
2. Did you try minikube delete before trying minikube start?

[frbimo]

@mariocoloma

1. Yes.
2. As i remember, i didn't.