set_parameter failed to set for specific vhost

[arouene]

Hello,

Having problem to set a parameter with set_parameter for a specific vhost.

As stated by rabbitmqctl, we can use the -p vhost parameter.

Usage:
rabbitmqctl [-n <node>] [-t <timeout>] [-q] set_parameter [-p <vhost>] <component_name> <name> <value>

But while I'm using it, the parameter is listed in the default "/" vhost.

Steps to reproduce

# rabbitmqctl set_parameter -p prd federation-upstream node01 '{"uri":"amqp://user:password@server/prd","ack-mode":"on-publish","trust-user-id":true,"message-ttl":300000}'
Setting runtime parameter "federation-upstream" for component "node01" to "{"uri":"amqp://user:password@server/prd","ack-mode":"on-publish","trust-user-id":true,"message-ttl":300000}" ...
# rabbitmqctl list_parameters -p prd
Listing runtime parameters for vhost "prd" ...

# rabbitmqctl list_parameters
Listing runtime parameters for vhost "/" ...
federation-upstream     node01  {"ack-mode":"on-publish","message-ttl":300000,"trust-user-id":true,"uri":"amqp://user:password@server/prd"}

Infos

• RabbitMQ version : 3.7.0
• Erlang version : 20.1
• RabbitMQ plugin information via rabbitmq-plugins list:

  # rabbitmq-plugins list
  Configured: E = explicitly enabled; e = implicitly enabled
  | Status: * = running on rabbit@server
  |/
  [  ] rabbitmq_amqp1_0                  3.7.0
  [  ] rabbitmq_auth_backend_cache       3.7.0
  [  ] rabbitmq_auth_backend_http        3.7.0
  [  ] rabbitmq_auth_backend_ldap        3.7.0
  [  ] rabbitmq_auth_mechanism_ssl       3.7.0
  [  ] rabbitmq_consistent_hash_exchange 3.7.0
  [  ] rabbitmq_event_exchange           3.7.0
  [E*] rabbitmq_federation               3.7.0
  [  ] rabbitmq_federation_management    3.7.0
  [  ] rabbitmq_jms_topic_exchange       3.7.0
  [E*] rabbitmq_management               3.7.0
  [e*] rabbitmq_management_agent         3.7.0
  [  ] rabbitmq_mqtt                     3.7.0
  [  ] rabbitmq_peer_discovery_aws       3.7.0
  [  ] rabbitmq_peer_discovery_common    3.7.0
  [  ] rabbitmq_peer_discovery_consul    3.7.0
  [  ] rabbitmq_peer_discovery_etcd      3.7.0
  [  ] rabbitmq_peer_discovery_k8s       3.7.0
  [  ] rabbitmq_random_exchange          3.7.0
  [  ] rabbitmq_recent_history_exchange  3.7.0
  [  ] rabbitmq_sharding                 3.7.0
  [  ] rabbitmq_shovel                   3.7.0
  [  ] rabbitmq_shovel_management        3.7.0
  [  ] rabbitmq_stomp                    3.7.0
  [  ] rabbitmq_top                      3.7.0
  [  ] rabbitmq_tracing                  3.7.0
  [  ] rabbitmq_trust_store              3.7.0
  [e*] rabbitmq_web_dispatch             3.7.0
  [  ] rabbitmq_web_mqtt                 3.7.0
  [  ] rabbitmq_web_mqtt_examples        3.7.0
  [  ] rabbitmq_web_stomp                3.7.0
  [  ] rabbitmq_web_stomp_examples       3.7.0

• Operating system : Ubuntu 16.04.3

[lukebakken]

Thanks Aurélien for the detailed description. I can reproduce what you report and am investigating. It looks to be specific to set_parameter in rabbitmqctl

[lukebakken]

@shengis - this is definitely an issue with the rabbitmqctl command, so I opened rabbitmq/rabbitmq-cli#232

As a workaround, you should be able to execute this command:

rabbitmqctl eval 'J="{\"uri\":\"amqp://user:password@server/prd\",\"ack-mode\":\"on-publish\",\"trust-user-id\":true,\"message-ttl\":300000}", rabbit_runtime_parameters:parse_set(<<"prd">>, <<"federation-upstream">>, "node01", J, "guest").'

I ran that command and verified it:

$ rabbitmqctl list_parameters -p prd
Listing runtime parameters for vhost "prd" ...
federation-upstream     "node01"        {"ack-mode":"on-publish","message-ttl":300000,"trust-user-id":true,"uri":"amqp://user:password@server/prd"}

[michaelklishin]

As a workaround you can define federation upstreams using the federation-management plugin.

[arouene]

Thanks for the workarounds ! To be faire, I didn't tried to use the UI management. It's easier to use command line when using remote servers.