-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Federation not working for quorum #844
Comments
Hi @Zerpet . Please find below details for recreating the issue: Earlier versions we used in both RabbitMQ before upgrade were as below -> RABBITMQ Image : 3.11.18-management
Versions we used in both RabbitMQ after upgrade are as below -> RABBITMQ Image : 3.13.2-management
We have enabled mtls in one of the rabbitmq. Scenario:
But, even after changing amqps to amqp in federation URI, it still stucked in starting state. Format for federation in yaml is same as given in above question. Issue is, I am unabke to get the federated queue type as quorum in upstream RMQ. I will really appreciate if you could you let me know how to add parameter queue type in kind: federation? Thank you so much for the support. |
I'm afraid it is not possible to define the queue type in |
Hi Team,
I have deployed 3 node RMQ cluster and operator on Azure kubernetes cluster.
Versions:
RMQ: 3.13.2-management
RMQ cluster operator: rabbitmqoperator/cluster-operator:2.9.0
controller-gen.kubebuilder.io/version: v0.14.0
RMQ messaging topology operator: rabbitmqoperator/messaging-topology-operator:1.14.2
controller-gen.kubebuilder.io/version: v0.15.0
mtls is on in downstream, and certificates are given in upstream.
Since classic has been deprecated, we have upgraded to quorum. The federation used before was as below:
apiVersion: rabbitmq.com/v1beta1
kind: Federation
metadata:
name: federation-example
spec:
name: "origin"
vhost: "downstream"
uriSecret:
name: federation-uri
ackMode: "on-confirm"
rabbitmqClusterReference:
name: example-rabbit
But it was showing error. The federation link created in Upstream queue refers to classic, whereas all the queues are in quorum.
Also the vhost in both Upstream and downstream have defaultQueueType is quorum.
Could you please support?
But when I added it through dashboard, and applied queuetype as quorum, it is working fine.
But, how can I add queuetype in yaml file. I added as below but even if it didn't show any error while applying, it is not taking that configuration.
apiVersion: rabbitmq.com/v1beta1
kind: Federation
metadata:
name: federation-example
spec:
name: "origin"
vhost: "downstream"
queue: quorum
I would really appreciate if you could support at earliest.
The text was updated successfully, but these errors were encountered: