Created attachment 693343 [details] screenshot of new host detected Description of problem: Gluster sync reporting incorrectly- New hosts are detected in the cluster even though no hosts were added from the CLI Version-Release number of selected component (if applicable): rhsc-2.1.0-0.qa5 How reproducible: Always Steps to Reproduce: 1. Create a new cluster 2. Add a server using the hostname 3. Once done, add a second server using the IP 4. When the hosts are UP, select the cluster and see the "General" sub-tab. You will see the following: "Action Items Some new hosts are detected in the cluster. You can Import them to oVirt engine or Detach them from the cluster." Now if you click on 'Import', it will actually show the IP of the host which has been added from the UI using the hostname. If you proceed further by giving the root password, it will actually try to add that same host but the install will fail. Actual results: It's reporting incorrectly as new hosts are detected even though no new hosts are added from the CLI. Expected results: It shouldn't detect the same server present in the cluster even when no action is done from the CLI Additional info: Screenshots attached
Created attachment 693344 [details] screenshot of import
Created attachment 693345 [details] screenshot of the hosts in the cluster
gluster peer status from both the hosts: [root@rhs-client29 ~]# gluster peer status Number of Peers: 1 Hostname: 10.70.36.54 Port: 24007 Uuid: 31c9d4e1-2c15-44e0-9ef6-28f11cf6bb30 State: Peer in Cluster (Connected) [root@rhs-client30 ~]# gluster peer status Number of Peers: 1 Hostname: 10.70.36.53 Port: 24007 Uuid: 31f97311-6fcc-4363-85ad-54813e1337ec State: Peer in Cluster (Connected)
Per Feb-06 bug triage meeting, targeting for 2.1.0.
*** Bug 915565 has been marked as a duplicate of this bug. ***
*** Bug 915567 has been marked as a duplicate of this bug. ***
*** Bug 918728 has been marked as a duplicate of this bug. ***
verified in 2.1.0-0.qa7.el6rhs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html