Bug 850434

Summary: Sync configuration with GlusterFS
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vidya Sakar <vinaraya>
Component: rhscAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: Prasanth <pprakash>
Severity: urgent Docs Contact:
Priority: medium    
Version: 2.1CC: gluster-bugs, jebrown, mmahoney, pprakash, rfortier, sdharane, shaines, ssampat
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 22:25:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vidya Sakar 2012-08-21 15:11:51 UTC
Any changes made to the storage cluster using commandline (like setting volume options, adding more bricks etc), those changes should be reflected in the GUI.

Comment 2 Shireesh 2012-10-31 10:15:50 UTC
Upstream patch for periodically syncing gluster configuration with engine DB:

http://gerrit.ovirt.org/7288

Comment 3 Shireesh 2012-11-16 09:39:10 UTC
One more patch: http://gerrit.ovirt.org/9135

These patches have been pulled to downstream as part of the periodic rebase. So this feature is now available in the latest QE drop.

Comment 4 Prasanth 2012-11-27 06:53:28 UTC
Moving the bug back to ASSIGNED as this feature is not working (Bug 879125) in the latest QE drop: rhsc-2.1-qa18.el6ev.noarch

Comment 5 Shireesh 2012-12-03 12:10:31 UTC
This is happening only in case the system contains replicate or stripe volumes. It is possible to test the feature by having only distribute type of volumes in the setup.

Comment 6 Shireesh 2012-12-11 12:26:39 UTC
*** Bug 844345 has been marked as a duplicate of this bug. ***

Comment 7 Prasanth 2012-12-20 10:28:35 UTC
Verified in Red Hat Storage Console Version: 2.1-qa18.el6ev

Comment 10 Scott Haines 2013-09-23 22:25:19 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