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

manases13 · 2019-03-27T19:24:21Z

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 · 2019-03-27T20:20:14Z

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 · 2019-03-29T07:53:36Z

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 · 2019-04-08T17:20:38Z

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 · 2019-04-09T08:31:49Z

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 · 2019-04-26T18:18:22Z

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 <index .secrets 0>: 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 · 2019-04-29T14:57:07Z

Hi, Do you guys know how to fix it?

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

pendenaor · 2019-05-02T15:12:36Z

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 · 2019-05-13T18:32:34Z

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 · 2019-06-03T08:48:24Z

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 · 2019-07-02T01:41:12Z

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 · 2019-07-02T09:51:57Z

@frbimo 2 things

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

frbimo · 2019-07-05T01:25:50Z

@mariocoloma

Yes.
As i remember, i didn't.

bhoopeshkumaar · 2021-03-12T17:18:56Z

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!

Worked after minikube delete and start. Thanks.

tstromberg added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 27, 2019

tstromberg changed the title ~~error~~ Problems detected in "kube-addon-manager": error: no objects passed tpod Mar 27, 2019

tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 4, 2019

tstromberg changed the title ~~Problems detected in "kube-addon-manager": error: no objects passed tpod~~ Invalid problem detection: "kube-addon-manager": error: no objects passed tpod Apr 5, 2019

tstromberg added this to the v1.0.1-candidate milestone Apr 5, 2019

tstromberg added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Apr 9, 2019

sharifelgamal self-assigned this Apr 10, 2019

sharifelgamal mentioned this issue Apr 10, 2019

Avoid surfacing "error: no objects passed to apply" non-error from addon-manager #4076

Merged

tstromberg closed this as completed in #4076 Apr 10, 2019

tstromberg mentioned this issue Jul 16, 2019

Problems detected in "kube-addon-manager" #4750

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

manases13 commented Mar 27, 2019

tstromberg commented Mar 27, 2019 •

edited

Loading

waynewyang commented Mar 29, 2019

cixuuz commented Apr 8, 2019

zackzhangkai commented Apr 9, 2019

thanusivan commented Apr 26, 2019

edwardstudy commented Apr 29, 2019 •

edited

Loading

pendenaor commented May 2, 2019 •

edited

Loading

mifiguer commented May 13, 2019

mariocoloma commented Jun 3, 2019

frbimo commented Jul 2, 2019

mariocoloma commented Jul 2, 2019

frbimo commented Jul 5, 2019

bhoopeshkumaar commented Mar 12, 2021

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

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

Comments

manases13 commented Mar 27, 2019

tstromberg commented Mar 27, 2019 • edited Loading

waynewyang commented Mar 29, 2019

cixuuz commented Apr 8, 2019

zackzhangkai commented Apr 9, 2019

thanusivan commented Apr 26, 2019

edwardstudy commented Apr 29, 2019 • edited Loading

pendenaor commented May 2, 2019 • edited Loading

mifiguer commented May 13, 2019

mariocoloma commented Jun 3, 2019

frbimo commented Jul 2, 2019

mariocoloma commented Jul 2, 2019

frbimo commented Jul 5, 2019

bhoopeshkumaar commented Mar 12, 2021

tstromberg commented Mar 27, 2019 •

edited

Loading

edwardstudy commented Apr 29, 2019 •

edited

Loading

pendenaor commented May 2, 2019 •

edited

Loading