I've been able to reproduce the cluster race condition occurs on multiple providers and different environments: - OpenStack-on-Openstack - On bare metal, with 1 phys. machine per juju unit - In lxc with the local provider
Reproduce by iterating this bundle over precise-icehouse, trusty-icehouse, trusty-juno and vivid-kilo: http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/dev/rabbitmq-cluster.yaml
Iteration script may be helpful: http://bazaar.launchpad.net/~1chb1n/+junk/yard/view/head:/charm-tests/rmq-cluster-cycle.sh
Or reproduce and exercise by enabling and running the new amulet tests in WIP merge proposal: https://code.launchpad.net/~1chb1n/charms/trusty/rabbitmq-server/next.amulet-fix-20-delay
I've been able to reproduce the cluster race condition occurs on multiple providers and different environments: on-Openstack
- OpenStack-
- On bare metal, with 1 phys. machine per juju unit
- In lxc with the local provider
Reproduce by iterating this bundle over precise-icehouse, trusty-icehouse, trusty-juno and vivid-kilo: bazaar. launchpad. net/~ost- maintainers/ openstack- charm-testing/ trunk/view/ head:/bundles/ dev/rabbitmq- cluster. yaml
http://
Iteration script may be helpful: bazaar. launchpad. net/~1chb1n/ +junk/yard/ view/head: /charm- tests/rmq- cluster- cycle.sh
http://
Or reproduce and exercise by enabling and running the new amulet tests in WIP merge proposal: /code.launchpad .net/~1chb1n/ charms/ trusty/ rabbitmq- server/ next.amulet- fix-20- delay
https:/