本文介绍了在Kubernetes中安装稳定的RabbitMQ时,获取MountVolume.SetUp的卷失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在通过头盔安装进行RabbitMQ安装时,我遇到了错误消息.

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

以下是kubectl版本的详细信息:

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"}

下面是我用来安装稳定的Rabbitmq的命令.

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

任何帮助将不胜感激.

谢谢.

推荐答案

这对我来说很好.看来这是与有关的问题,在这种情况下,它无法安装ConfigMap Rabbitmq配置所在的卷: .某些情况下,也可能阻止了节点上的卷装载(进程,文件描述符等).

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).

您没有指定在哪里运行,但是您可以尝试弹跳节点组件:kubelet,docker,最后是您的节点.请记住,节点上运行的所有其他容器都将在群集中的某处重新启动.

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.

kubectl客户端,kubectl版本和kubeadm版本之间不匹配.

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

这篇关于在Kubernetes中安装稳定的RabbitMQ时,获取MountVolume.SetUp的卷失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-23 14:40