Strange management UI behavior while upgrading from 4.0.5 to 4.1.4

30 views

Skip to first unread message

Neilerua Neilerua

unread,

Sep 10, 2025, 11:15:06 AM (9 days ago) Sep 10

to rabbitmq-users

Hello,

After upgrading successfully rabbitmq from version 4.0.5 to 4.1.4, we observe that feature flags list is different between command line and management ui admin / feature flag menu.

In Management UI we have :

detailed_queues_endpoint

khepri_db

message_containers_deaths_v2

quorum_queue_non_voters

rabbit_exchange_type_local_random

rabbitmq_4.0.0

(NB : only khepri is disabled)

In command line (list_feature_flags) :

Listing feature flags ...
name state
classic_mirrored_queue_version enabled
classic_queue_type_delivery_support enabled
detailed_queues_endpoint enabled
direct_exchange_routing_v2 enabled
drop_unroutable_metric enabled
empty_basic_get_metric enabled
feature_flags_v2 enabled
implicit_default_bindings enabled
khepri_db disabled
listener_records_in_ets enabled
maintenance_mode_status enabled
message_containers enabled
message_containers_deaths_v2 enabled
quorum_queue enabled
quorum_queue_non_voters enabled
rabbit_exchange_type_local_random enabled
rabbitmq_4.0.0 enabled
rabbitmq_4.1.0 enabled
restart_streams enabled
stream_filtering enabled
stream_queue enabled
stream_sac_coordinator_unblock_group enabled
stream_single_active_consumer enabled
stream_update_config_command enabled
tracking_records_in_ets enabled
user_limits enabled
virtual_host_metadata enabled