Created attachment 838319 [details]
screenshot

Description of problem:
------------------------

When a server is added to a cluster managed by RHSC, such that the gluster UUID of the server is same as that of another server already present in the cluster, the following messages are seen in the events log - 

State was set to Up for host server1-clone.
Gluster UUID of host server1-clone on Cluster test already exists.
Failed to fetch gluster peer list from server server1-clone on Cluster test.

( see attached screenshot )

After the host is set to non-operational because of duplicate UUID, it should not be attempted to fetch the peer list.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.2-0.27.beta.el6_5 

How reproducible:
Always

Steps to Reproduce:
1. Added a server to a cluster managed by RHSC, waited for it to come up.
2. Added another server to the same cluster, this server had the same gluster UUID as the first one ( achieved by means of cloning the VM )

Actual results:
The server was moved to Non-operational mode after installation. The above described events log messages are seen.

Expected results:
The peer list on the server should not be fetched after it is known to be non-operational because of duplicate UUID.

Additional info: