Bug 907830 - [RHSC]: Gluster sync reporting incorrectly- New hosts are detected in the cluster even though no hosts were added from the CLI
Summary: [RHSC]: Gluster sync reporting incorrectly- New hosts are detected in the clu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: Prasanth
URL:
Whiteboard:
: 915565 915567 918728 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 11:11 UTC by Prasanth
Modified: 2013-09-23 22:25 UTC (History)
6 users (show)

Fixed In Version: qa7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:25:38 UTC
Embargoed:


Attachments (Terms of Use)
screenshot of new host detected (100.02 KB, image/png)
2013-02-05 11:11 UTC, Prasanth
no flags Details
screenshot of import (121.25 KB, image/png)
2013-02-05 11:12 UTC, Prasanth
no flags Details
screenshot of the hosts in the cluster (94.57 KB, image/png)
2013-02-05 11:12 UTC, Prasanth
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 12021 0 None None None Never

Description Prasanth 2013-02-05 11:11:17 UTC
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

Comment 1 Prasanth 2013-02-05 11:12:12 UTC
Created attachment 693344 [details]
screenshot of import

Comment 2 Prasanth 2013-02-05 11:12:40 UTC
Created attachment 693345 [details]
screenshot of the hosts in the cluster

Comment 4 Prasanth 2013-02-05 11:16:43 UTC
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)

Comment 6 Scott Haines 2013-02-06 20:49:32 UTC
Per Feb-06 bug triage meeting, targeting for 2.1.0.

Comment 7 Shireesh 2013-03-01 07:26:17 UTC
*** Bug 915565 has been marked as a duplicate of this bug. ***

Comment 8 Shireesh 2013-03-01 07:55:58 UTC
*** Bug 915567 has been marked as a duplicate of this bug. ***

Comment 9 Shireesh 2013-03-08 09:52:04 UTC
*** Bug 918728 has been marked as a duplicate of this bug. ***

Comment 10 Dustin Tsang 2013-03-08 18:30:33 UTC
verified in 2.1.0-0.qa7.el6rhs

Comment 12 Scott Haines 2013-09-23 22:25:38 UTC
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


Note You need to log in before you can comment on or make changes to this bug.