-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Management UI creates classic queue instead of virtual host default queue type in some circumstances #11088
Comments
Sorry, I forgot to mention this was identified on RabbitMQ 3.13.0 and repeated on 3.13.1. |
I would say its intentional:
The alternative would be to always patch the args and later fail. |
Quorum queues and streams never meant to be durable. In 4.x, transient entities will no longer exist. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In the management UI, when I go to create a new queue and elect to use the
Default for virtual host
, I am presented with the queueDurability
selector. When the virtual host default queue type isquorum
orstream
, selectingTransient
will give me aclassic
queue instead. SelectingDurable
gives me the expected queue type.When selecting
quorum
orstream
as the queueType
instead ofDefault for virtual host
, theDurability
selector disappears.Reproduction steps
quorum
orstream
as the default queue typeQueues and Streams
tabVirtual host
selectorDefault for virtual host
for the queueType
selectorDurability
selector visibleTransient
for theDurability
selectorclassic
queueExpected behavior
The
Durability
selector should not be shown when the default queue type for that virtual host isquorum
orstream
.It should also not give me a
classic
queue when I selectTransient
but rather an error message (debatable as fixing the above expected behaviour would render the error message irrelevant).Additional context
No response
The text was updated successfully, but these errors were encountered: