Take note that the rabbitmq-server/next amulet tests are being refactored to be in line with other os-charms, to exercise more than just Trusty, and to fix misc issues in logic which are causing false passes.
Those new and refactored tests have are still in review, but have exposed two critical bugs. I would recommend holding on this proposal until the following bugs are resolved and the corresponding branches have landed in next. Then, I'd rebase your proposal and let the updated tests re-run to make sure everything still passes.
Take note that the rabbitmq- server/ next amulet tests are being refactored to be in line with other os-charms, to exercise more than just Trusty, and to fix misc issues in logic which are causing false passes.
Those new and refactored tests have are still in review, but have exposed two critical bugs. I would recommend holding on this proposal until the following bugs are resolved and the corresponding branches have landed in next. Then, I'd rebase your proposal and let the updated tests re-run to make sure everything still passes.
bug tldrs:
cluster race bug, affects stable and next /bugs.launchpad .net/charms/ +source/ rabbitmq- server/ +bug/1486177
>50% fail to cluster with leadership election
>90% fail to cluster without leadership election
https:/
outright fail on vivid, affects stable and next /bugs.launchpad .net/charms/ +source/ rabbitmq- server/ +bug/1485722
100% fail, rmq's pidfile location changed, cron job errors out
https:/