Issue with RabbitMQ Deployment Using Existing PVC and Replication Setup

[prathi-adeptia]

Describe the bug

We are encountering an issue while deploying RabbitMQ with an existing PVC configuration in a Kubernetes environment.

Steps Taken:
Successfully deployed RabbitMQ on a single node using an existing Persistent Volume Claim (PVC). The node operates as expected.
Attempted to scale the deployment by adding replicas to enable RabbitMQ clustering.
Observed Behavior:
The first node continues to work without issues.
Additional replicas fail to start with errors indicating potential issues with the PVC or volume sharing.
Configuration Details:
RabbitMQ version: [Specify version]
Kubernetes platform: [e.g., AKS]
PVC Storage Class: [Provide details, e.g., ReadWriteOnce or ReadWriteMany]
Helm Chart: [Provide details, e.g., Bitnami Helm chart]
appVersion: 3.12.2
helm version: 12.0.8
Logs from failing pods: [Include specific error logs]

rabbitmq-logs.log

Reproduction steps

1. Download and extract the RabbitMQ Bitnami helm chart.
2. Update property in values.yaml "existingClaim: "pv-claim-name""
3. Deploy RabbitMQ using helm chart
   ...

Expected behavior

Expected Behavior:
All replicas should start successfully and form a RabbitMQ cluster while sharing or utilizing PVCs correctly.

Additional context

No response

[mkuratczyk]

This is not about PVC sharing but about peer discovery. We can't really help since you didn't mention the version of RabbitMQ and you only share a tiny snippet of the logs from one of the nodes.

[prathi-adeptia]

Bitnami RabbtiMQ
appVersion: 3.12.2
helm version: 12.0.8
I have configured existing pvc in "existingClaim" in values.yaml and replicas with 3.

 ## @param persistence.existingClaim Provide an existing PersistentVolumeClaims
  ## The value is evaluated as a template
  ## So, for example, the name can depend on .Release or .Chart
  ##
  existingClaim: ""

The Rabbitmq first node (xxx-xx-rabbitmq-o) started successfully. but second node (xxx-xx-rabbitmq-1) throws "exception exit: inconsistent_cluster"

[mkuratczyk]

RabbitMQ 3.12 is out of support and there has been significant changes in this part of the code in both 3.13 and 4.0.
If this happens with 4.0, we will investigate.

https://www.rabbitmq.com/release-information