Skip to content
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

Queue arguments are not re-concealed #822

Closed
kamikaze opened this issue May 17, 2024 · 1 comment · Fixed by #830
Closed

Queue arguments are not re-concealed #822

kamikaze opened this issue May 17, 2024 · 1 comment · Fixed by #830
Labels
bug Something isn't working
Milestone

Comments

@kamikaze
Copy link

Describe the bug

Queue arguments are not being re-concealed after initial values are set.

To Reproduce

Steps to reproduce the behavior:

  1. define x-message-ttl to let's say 30000
  2. apply
  3. change x-message-ttl to 60000
  4. change is not being applied
apiVersion: rabbitmq.com/v1beta1
kind: Queue
metadata:
  name: jobs-delayed
  namespace: test
spec:
  name: "jobs_delayed"
  vhost: test
  type: quorum
  arguments:
    x-message-ttl: 60000
    x-dead-letter-exchange: "xchg_jobs"
    x-dead-letter-routing-key: "job"
  autoDelete: false
  durable: true
  rabbitmqClusterReference:
    name: rabbitmq

Expected behavior
x-message-ttl set to 60000

Version and environment information

  • Messaging Topology Operator: bitnami/rmq-messaging-topology-operator:1.14.1-debian-12-r1
  • RabbitMQ: bitnami/rabbitmq:3.13.2-debian-12-r4
  • RabbitMQ Cluster Operator: bitnami/rabbitmq-cluster-operator:2.9.0-debian-12-r1
  • Kubernetes: v1.29.4+k3s1
@kamikaze kamikaze added the bug Something isn't working label May 17, 2024
@Zerpet
Copy link
Contributor

Zerpet commented May 21, 2024

This is expected behaviour. Queue arguments can't be changed in RabbitMQ after declaration. We have to update the webhook to forbid updates in queue arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants