Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1693149

Summary: [Day 2] With expand cluster, newly added nodes are not added in to the existing gluster cluster
Product: [oVirt] cockpit-ovirt Reporter: Mugdha Soni <musoni>
Component: gluster-ansibleAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: Mugdha Soni <musoni>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.12.5CC: bugs, rhs-bugs, sabose, sasundar
Target Milestone: ovirt-4.3.6Keywords: ZStream
Target Release: 0.13.6Flags: sasundar: ovirt-4.3?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.13.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1693144 Environment:
Last Closed: 2019-09-26 19:43:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1693144    
Attachments:
Description Flags
Screenshot of peers not added.
none
Screenshot of different cluster formed. none

Description Mugdha Soni 2019-03-27 09:04:23 UTC 
Created attachment 1548431 [details]
Screenshot of peers not added.

+++ This bug was initially created as a clone of Bug #1693144 +++

Description of problem:
------------------------
While expanding cluster,the deployment is successful but the peers are not probed and a different cluster is formed whereas it should be added to the existing cluster. 

Version-Release number of selected component:
---------------------------------------------
rhvh-4.3.0.5-0.20190313
glusterfs-server-3.12.2-47.el7rhgs

gluster-ansible-repositories-1.0-1.el7rhgs.noarch
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-features-1.0.4-5.el7rhgs.noarch
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-roles-1.0.4-4.el7rhgs.noarch
gluster-ansible-infra-1.0.3-3.el7rhgs.noarch


How reproducible:
------------------
3/3

Steps to Reproduce:
----------------------
1.After the successful gluster deployment log in to cockpit UI and click on hosted engine .
2.Start with expanding cluster.
3.User will have a successful deployment but when user will issue the command " gluster peer status " , the peers will not be connected.

Actual results:
-----------------
The additional machines/peers form a seperate cluster.

Expected results:
-------------------
The peers which are used to expand the cluster should be a part of existing 
cluster and should not for a different cluster .

--- Additional comment from Mugdha Soni on 2019-03-27 09:01 UTC ---
Comment 1 Mugdha Soni 2019-03-27 09:05:33 UTC 
Created attachment 1548432 [details]
Screenshot of different cluster formed.
Comment 2 SATHEESARAN 2019-09-04 02:20:41 UTC 
Tested with cockpit-ovirt-dashboard-0.13.7

Expand cluster operation from day2 operation resulted in addition of 3 nodes
to the existing cluster of 3 nodes
Comment 3 Sandro Bonazzola 2019-09-26 19:43:02 UTC 
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.