Bug 970769 - [RHSC] Volume Start via Gluster CLI does not sync with RHSC
[RHSC] Volume Start via Gluster CLI does not sync with RHSC
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
Unspecified Unspecified
high Severity unspecified
: ---
: RHGS 2.1.0
Assigned To: Sahina Bose
Matt Mahoney
Depends On:
  Show dependency treegraph
Reported: 2013-06-04 15:52 EDT by Matt Mahoney
Modified: 2015-05-13 11:52 EDT (History)
6 users (show)

See Also:
Fixed In Version: bb5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-23 18:25:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sync Volume Start (6.10 MB, application/x-tar)
2013-06-04 15:52 EDT, Matt Mahoney
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 15381 None None None Never

  None (edit)
Description Matt Mahoney 2013-06-04 15:52:32 EDT
Created attachment 756941 [details]
Sync Volume Start

Description of problem:
When starting a Distribute Volume via Gluster CLI, the volume does start but does not sync with RHSC.

Gluster Volume Info:

Volume Name: demo-distribute1
Type: Distribute
Volume ID: b7b74dc0-ddeb-4633-b86f-b10012d6ffb6
Status: Started
Number of Bricks: 4
Transport-type: tcp

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:
Console should sync with volume started by Gluster CLI.

Additional info:
Comment 2 Sahina Bose 2013-06-05 04:38:13 EDT
Related to Bug 970759, there was an exception in getting volume list, and so the sync did not succeed.
Comment 4 Scott Haines 2013-09-23 18:25:44 EDT
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.


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