After upgrading to 3.13, management interface shows 500 for /api/deprecated-features/used #10640
-
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 1 reply
-
@leonjoosse what does the node log when this happens? |
Beta Was this translation helpful? Give feedback.
-
Thanks for the swift reply @michaelklishin I had a better look at the logs. I thought this was unrelated, but it is printed everytime I execute the request via Insomnia. Using the cURL request from the start post, this is logged:
|
Beta Was this translation helpful? Give feedback.
-
Interesting. Would it be possible to see the policies you have running too @leonjoosse ? |
Beta Was this translation helpful? Give feedback.
-
Thank you for the report! I see the internal format of the policy is an Erlang map instead of the expected Erlang proplist. How do you declare the policy in the first place? |
Beta Was this translation helpful? Give feedback.
-
@SimonUnge @dumbbell Thanks for getting back on this. Here's the policies we defined. Only added them via the UI, they are there for quite a while already. Unfortunately, I don't know on which RabbitMQ version we added them. The colleague usually managing the system got back today, on his advice I removed both policies. The error as described in the start post was immediately gone. I added both policies again, using the UI, with the exact same parameters. This works for me, so closed the issue for now. If you have more questions, I'm happy to answer them! |
Beta Was this translation helpful? Give feedback.
-
Thank you for the additional feedback! So somehow, the policy has been stored internally in an invalid format, despite the validity checks. The web UI itself can’t bypass these checks, so there must be something else going on. Another question: did you used the definitions import/export feature? |
Beta Was this translation helpful? Give feedback.
-
Moved to a discussion since we are still narrowing down what may be going on and where. |
Beta Was this translation helpful? Give feedback.
-
@leonjoosse If you happen to have the information on what version the policy was added, it would help narrow it down, or perhaps you have some idea at least of which version of RabbitMQ you started out with at some point? |
Beta Was this translation helpful? Give feedback.
-
I got hit by this too, also fixed by re-creating all policies I had 1 user policy and 1 operator policy, both most likely created long ago on rabbitmq 3.8 via the management UI |
Beta Was this translation helpful? Give feedback.
-
Even if it's not related to upgrading from an earlier version of RabbitMQ I will take the chance to ask if this is related somehow to the issue that started this thread? By just creating a fresh instance of RabbitMQ 3.13.2, using Docker on my local machine, I'm seem to be able to reproduce the issue by importing definitions created on same version of RabbitMQ. The steps I have performed to reproduce it is the following
|
Beta Was this translation helpful? Give feedback.
-
Yes, I can confirm that for me the issue is also related to definitions import (the affected policies are actually defined in a definitions.json file that I import on every startup of rabbitmq) |
Beta Was this translation helpful? Give feedback.
-
@cvijdea-bd @johnnycederholm this was fixed recently - #11193 |
Beta Was this translation helpful? Give feedback.
@cvijdea-bd @johnnycederholm this was fixed recently - #11193
#11192