Similar behavior as bug 1529861
deploy succeeded, then one of the nodes says it's up in corosync, but is really down and there's no rabbitmq-server process running.
Similar behavior as bug 1529861
deploy succeeded, then one of the nodes says it's up in corosync, but is really down and there's no rabbitmq-server process running.