Bug 928531 - [RHSC] Create Volume Failure
Summary: [RHSC] Create Volume Failure
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Shireesh
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-27 20:42 UTC by Matt Mahoney
Modified: 2013-07-03 06:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-28 15:26:37 UTC
Embargoed:


Attachments (Terms of Use)
Create Volume Failure (136.25 KB, application/zip)
2013-03-27 20:42 UTC, Matt Mahoney
no flags Details

Description Matt Mahoney 2013-03-27 20:42:57 UTC
Created attachment 717282 [details]
Create Volume Failure

Description of problem:
Create Distribute volume with two bricks resulted in failure in UI to create the volume, but the volume was still created in Gluster.

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

QA9
RHS-2.0-20130320.2

How reproducible:


Steps to Reproduce:
1. Create Distribute volume with two brick
2.
3.
  
Actual results:
Create Volume Dialog error:
"Error while executing action Create Gluster Volume: Unexpected exception"

Expected results:
Volume should be created with no failures.

Additional info:

Comment 3 Kanagaraj 2013-03-28 05:36:51 UTC
please provide glusterfs and vdsm versions

Comment 4 Sahina Bose 2013-03-28 05:59:20 UTC
(In reply to comment #3)
> please provide glusterfs and vdsm versions

192.168.122.163 - This host is non-operational.
Are the two hosts using the same vdsm version, i.e are these both RHS-2.0-20130320.2

QA9 should not work with RHS-2.0+ unless vdsm and gluster versions are updated to latest.

Comment 5 Matt Mahoney 2013-03-28 15:26:37 UTC
This was a compatibility issue with running RHS2.0+, and not with the latest glusterfs version required by QA9. Closing the bug.


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