Getting MountVolume.SetUp failed for volume while installing stable RabbitMQ in Kubernetes

11/2/2018

I am getting below error while doing the installation of RabbitMQ through helm install.

MountVolume.SetUp failed for volume "config-volume" : couldn't propagate object cache: timed out waiting for the condition

Below is the details of kubectl version:

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Pl
atform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:10:24Z", GoVersion:"go1.9.3", Compiler:"gc", Pla
tform:"linux/amd64"}

And below is the command I used to install stable rabbitmq.

helm install --name coa-rabbitmq --set rabbitmq.username=#Username#,rabbitmq.password=#Password#,rabbitmq.erlangCookie=#Cookie#,livenessProbe.periodSeconds=120,readinessProbe.periodSeconds=120 stable/rabbitmq

Any help will be appreciated.

Thanks in advance.

-- Bhushan Shah
kubernetes
kubernetes-helm
rabbitmq

1 Answer

11/3/2018

This works fine for me. Looks like it's an issue related to this in this case it can't mount the ConfigMap volume where the rabbitmq config is: the config-volume. It may also be the case that something is preventing mounting volumes on your nodes (process, file descriptor, etc).

You didn't specify where you are running this, but you can try bouncing your node components: kubelet, docker, and ultimately your node. Keep in mind that all other containers running on the node will restart somewhere again in the cluster.

Edit:

There was a mismatch between kubectl client, kubectl version and kubeadm version.

-- Rico
Source: StackOverflow