Queue management page not visible when the rabbitmq_stream_management plugin enabled and management_stats is disabled

[gomoripeti]

Describe the bug

RabbitMq version main @ 1a6f81b

When the rabbitmq_stream_management plugin is enabled and management_stats are disabled, if I try to visit the individual queue page of any queue type (not just streams) I get an error message "Stats in management UI are disabled on this node" and queue page does not load. If I disable the rabbitmq_stream_management plugin then basic info about the queue are visible which is the expected behaviour.

I only was able to dig as far as apart from a request to api/queues/VHOST/QUEUE (and api/queues/VHOST/QUEUE/bindings) if the rabbitmq_stream_management plugin is enabled there is also a request to api/stream/publishers/VHOST/QUEUE which returns 400 and {"error":"bad_request","reason":"Stats in management UI are disabled on this node"} in case mgmt stats are disabled. That extra request is probably defined here https://github.com/rabbitmq/rabbitmq-server/blob/main/deps/rabbitmq_stream_management/priv/www/js/stream.js#L17

Reproduction steps

1. Have rabbitmq_stream_management (and rabbitmq_management ) plugins enabled
2. Create a classic queue "cq1"
3. Disable mgmt stats in the erlang shell with application:set_env(rabbitmq_management, disable_management_stats, true).
4. Go to queues page of the Mgmt UI and click "cq1" queue -> error message "Stats in management UI are disabled on this node" displayed
5. rabbitmq-plugins disable rabbitmq_stream_management
6. Click "cq1" queue again -> the queue page loads fine (with reduced information of course)
   ...

Expected behavior

The queue page should still load and show basic information even if management stats are disabled and stream management plugin is enabled.

Additional context

No response

[MarcialRosales]

@gomoripeti this issue is pretty old and it is probably fixed because i cannot reproduce it. Can you please confirm it ?

[michaelklishin]

If someone knows how to reproduce it against 4.1.0, the issue can be reopened.

[lukebakken]

FWIW, I can't reproduce using 3.13.7.

[gomoripeti]

I can't reproduce either on a recent main. thanks for fixing it one way or the other.