RabbitMQ Cluster failed with 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims on Kubernetes #752
Comments
|
I tried installing RabbitMQ Operator and RabbitMQ Cluster using Docker Desktop's embedded Kubernetes on Windows I repeated the steps mentioned above ie Installed cluster-operator and created RabbitMQ Cluster Though RabbitMQ Cluster on Windows generated the following Warning pod came up successfully PS C:\RMO> kubectl get all -n rabbitmq-system Someone kindly let me know whether this issue is OS dependent or |
|
Firstly, probably not related to your issue, but around the time you raised this issue we released a new operator version, so if you run Looking at that error message, and only seeing it on one Kubernetes distribution of the two, makes me suspect that Dynamic Provisioning isn't being used. When setting up your CentOS Kubernetes cluster, did you either define any storage classes, or enable the DefaultStorageClass admission controller? If you did neither, then your cluster won't know how to automatically reserve disk for persistent volumes through Dynamic Provisioning, and you would have to create the Persistent Volumes yourself for the operator to then claim with a PVC. You have two options when deploying:
It might be useful to look at the output of |
|
As for your second question, you can use the statefulSet override feature to add additional fields to the StatefulSet template. In your case, that would look something like: apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
name: my-override-rabbit
spec:
override:
statefulSet:
spec:
template:
spec:
containers: []
hostAliases:
- ip: "127.0.0.1"
hostnames:
- "foo.local"
- "bar.local"
- ip: "10.1.2.3"
hostnames:
- "foo.remote"
- "bar.remote" |
|
@coro Thank you for responding quickly. Will try and update you tomorrow as it's late here |
|
On Windows Despite 'unbound immediate PersistentVolumeClaims' and 'Readiness probe' failures Windows opened up the required ports and kept the pod running PS C:\WINDOWS\system32> kubectl describe pod testrmc-server-0 -n rabbitmq-system | more On CentOS 7 and I am running K8S Cluster with 1 master and 1 worker node I see 3 different reasons (in 'logs', 'describe' and 'cluster definition') but not sure how to resolve them [root@re-ctrl01 tmp]# kubectl logs definition-server-0 -n rabbitmq-system (Tailored output) [root@re-ctrl01 tmp]# kubectl describe pod/definition-server-0 -n rabbitmq-system (Tailored output) [root@re-ctrl01 tmp]# kubectl describe rabbitmqcluster.rabbitmq.com/definition -n rabbitmq-system The following outputs were also added for your reference [root@re-ctrl01 ~]# kubectl exec pod/definition-server-0 -n rabbitmq-system -- tac /etc/hosts [root@re-devk8s-ctrl01 ~]# kubectl get pv [root@re-ctrl01 ~]# kubectl get pvc -n rabbitmq-system Kindly let me know had I done something wrong |
|
I added hostAliases to /etc/hosts file of rabbitmq docker container which resolved the issue but I am not sure whether it's correct Output of rabbitmq pod Though readiness probe failed I was able to test the connectivity If possible kindly let me know why 'readiness probe' fails ? |
|
This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring. |
|
Closing stale issue due to further inactivity. |
github-actions
bot
added
the
closed-stale
I am trying to install RabbitMQ Cluster Operator and RabbitMQ Cluster on K8S Cluster (bare metal server) by following the steps mentioned below
OS Version: CentOS Linux 7 (Core)
[root@re-ctrl01 tmp]# kubectl version
[root@re-ctrl01 tmp]# kubectl apply -f https://github.com/rabbitmq/cluster-operator/releases/latest/download/cluster-operator.yml
[root@re-ctrl01 tmp]# kubectl describe pod/test-rabbitmq-cluster-server-0 -n rabbitmq-system
Though POD was created it failed with
0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.The text was updated successfully, but these errors were encountered: