1. Fuel-master was set up, lets call it fuel-master-1
2. Fuel-master-1 discovered VMs with all necessary stuff which is needed to work with fuel-master-1 (including credentials to rabbitmq)
3. For some reasons fuel-master-1 was reinstalled into a new fuel-master-2 (which have generated new credentials to rabbitmq).
4. VMs that were discovered from fuel-master-1, connected to fuel-master-2, because fuel-master-2 has same ip addresses using nailgun-agent which doesn't require any authentication.
5. Credentials required to access rabbitmq, which are required for mcollective, mismatched.
6. Deployment fails.
Here is list of steps to reproduce the bug
1. Fuel-master was set up, lets call it fuel-master-1
2. Fuel-master-1 discovered VMs with all necessary stuff which is needed to work with fuel-master-1 (including credentials to rabbitmq)
3. For some reasons fuel-master-1 was reinstalled into a new fuel-master-2 (which have generated new credentials to rabbitmq).
4. VMs that were discovered from fuel-master-1, connected to fuel-master-2, because fuel-master-2 has same ip addresses using nailgun-agent which doesn't require any authentication.
5. Credentials required to access rabbitmq, which are required for mcollective, mismatched.
6. Deployment fails.