deploying clustered charm in manual provider causes incomplete relations without min-cluster-size set

Bug #1821402 reported by Jeff Hillman
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rabbitmq-server (Juju Charms Collection)

Bug Description

Deploying a 3 node RMQ cluster via charms in a juju manual provider scenario causes the cluster to form, but incomplete relations.

In this specific scenario, 1x haproxy unit, 3x landscape-server units, 3x postgresql units and 3x rabbitmq-server units.

All nodes deploy fine, and rabbit going to a "Unit is Ready and Clustered" state, however no information is passed to landscape-server (broker information), and thus it sits in an unknown state.

If rabbit is only deployed with 1 unit it all set up properly, and extra units can be added after the fact.

If rabbit is deployed with min-cluster-size: 3 in the bundle, then this behavior does not happen.

Using the provided bundle WITHOUT min-cluster-size set, this was reproduceable in a manual provider environment with VMware VMs, KVM VMs, and bare-metal MAAS on an OB. The Same bundle WITHOUT min-cluster-size set works with actual providers (AWS and MAAS).

Tags: cpe-onsite
Revision history for this message
Jeff Hillman (jhillman) wrote :
Changed in rabbitmq-server (Juju Charms Collection):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.