-
Notifications
You must be signed in to change notification settings - Fork 517
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
[22.10.0]inequivalent arg 'durable' for queue 'counters-0' in vhost '/': received 'false' but current is 'true' #774
Comments
Yeah I think the only way is to delete the queue so that sentry can recreate it with the proper arguments |
Isn't it easier to manage it directly in the helm with a job to launch at deployment time? |
Ideally yes. It would be nice to have that. |
I don't know how to do it myself, It's possible to manage that directly in the helm package for us ? |
I had this issue also, I solved it by shelling into the rabbitmq pod and executing rabbitmqctl delete_queue counters-0
rabbitmqctl delete_queue triggers-0 Then the worker seemed to work |
Deleting the solves the issue, i had to do it multiple since the upgrade. |
I can confirm the issue exists and the workaround mentioned by ocdi fixed the issue for us. |
Same Issue on 22.10.0 |
Any news ? |
I had to fix my rabbitmq definition. |
No news about this really annoyed problem ? Without this fix, I'm blocked in the 16.x chart version |
@throrin19 Does your rabbitmq loads a definition during the start? I had to update definition and issue was fixed. |
Just delete the old queue. |
@Mokto Normally using chart we don't have to do this manually, the chart does do all this migration things using jobs on helm upgrade @farodin91 I don't know how to do/verify this |
We experienced the same, also for a vanilla install. This resolved it. 🙏 |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
After update to the last Sentry version 22.10.0 (helm 17.6.0), I have this error in the Sentry Worker :
The text was updated successfully, but these errors were encountered: