Federation Validation Error on 3.7.6

[Charles Burton]

I'm trying to federate a new cluster with an existing broker as part of migrating from v3.6.15 to the latest 3.7.6.  On the 3.7.6 cluster I have verified that both federation plugins are enabled and the software has been restarted.  I have an upstream configured like this:
amqp://guest:[redacted]@10.0.14.234

I then try to add a policy and I'm noticing two things:

1) I can only select queues, there is no option for exchanges
2) When I try to create the policy it gives this error:

   [{<<"federation-upstream-set">>,<<"all">>}] are not recognised policy settings

[Michael Klishin]

How can we reproduce?

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Charles Burton]

I'm forming the cluster on AWS in ECS, but it essentially  goes like this:

echo " *** Configuring rabbit cluster"

    echo "loopback_users = none" >> ${RABBIT_CONFIG_FILE}

    echo "log.console.level = debug" >> ${RABBIT_CONFIG_FILE}

    echo "cluster_formation.peer_discovery_backend = rabbit_peer_discovery_dns" >> ${RABBIT_CONFIG_FILE}

    echo "cluster_formation.dns.hostname = ${NAMESPACE}" >> ${RABBIT_CONFIG_FILE}

rabbitmq-plugins enable rabbitmq_federation

rabbitmq-plugins enable rabbitmq_federation_management

rabbitmq-server

That creates the cluster using:
FROM rabbitmq:3.7.6-management


Once that cluster forms I went to the management UI -> Admin
then followed the docs to federate with the old cluster

On Tuesday, July 3, 2018 at 11:22:08 AM UTC-6, Michael Klishin wrote:

How can we reproduce?

On Tue, Jul 3, 2018 at 7:54 PM, Charles Burton <charles....@gmail.com> wrote:

I'm trying to federate a new cluster with an existing broker as part of migrating from v3.6.15 to the latest 3.7.6.  On the 3.7.6 cluster I have verified that both federation plugins are enabled and the software has been restarted.  I have an upstream configured like this:
amqp://guest:[redacted]@10.0.14.234

I then try to add a policy and I'm noticing two things:

1) I can only select queues, there is no option for exchanges
2) When I try to create the policy it gives this error:

   [{<<"federation-upstream-set">>,<<"all">>}] are not recognised policy settings

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

Charles,

I need your upstream [set] and policy definition. Your peer discovery configuration cannot possibly affect

upstream validation. Feel free to edit out sensitive values such as hostnames, IP addresses and so on.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Charles Burton]

Well, not sure what happened but I rebuilt the cluster changing how enabled the plugins with the --offline flag and now everything looks like it's working.

[Michael Klishin]

There were 3 or so validation errors resolved since 3.7.0, e.g. in 3.7.5 [1].

So perhaps the version wasn't what you expected it to be?

1. https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.7.5

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.