Bug 896166

Summary: volumes created on rhs 2.0 beta plus do not synchronize to rhsc QA4
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Dustin Tsang <dtsang>
Component: rhscAssignee: Shireesh <shireesh>
Status: CLOSED NOTABUG QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1CC: mmccune, rhs-bugs, shtripat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-17 14:18:48 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:
Attachments:
Description Flags
/var/log/ovirt-engine/engine.log none

Description Dustin Tsang 2013-01-16 18:56:18 UTC
Created attachment 679749 [details]
/var/log/ovirt-engine/engine.log

Description of problem:
volumes created on rhs 2.0 beta plus do not synchronize to rhsc QA4.
On the rhsc, the Engine log(/var/log/ovirt-engine/engine.log) contains NumberformatException.

Version-Release number of selected component (if applicable):
RHSC 2.1 QA4
RHS 2.0 beta plus

How reproducible:


Steps to Reproduce:
1. setup 3 machines (rhsc with 2 rhs nodes)
2. create a cluster from rhsc web interface
3. add each of the 2 rhs nodes as severs in the cluster
4. From the CLI in one of the rhs nodes, create a replicate volume.
gluster volume create sync-volume replicate replica 8 \
g1:/opt/gluster/bricks/replicate/brick1 \
g1:/opt/gluster/bricks/replicate/brick2 \
g1:/opt/gluster/bricks/replicate/brick3 \
g1:/opt/gluster/bricks/replicate/brick4 \
g2:/opt/gluster/bricks/replicate/brick1 \
g2:/opt/gluster/bricks/replicate/brick2 \
g2:/opt/gluster/bricks/replicate/brick3 \
g2:/opt/gluster/bricks/replicate/brick4
5. wait for volume to appear on rhsc web interface
  
Actual results:
volume never appears on rhsc web interface.
NumberformatException is thrown and captured in engine.log

Expected results:
volume appears on the rhsc web interface


Additional info:

Comment 2 Shireesh 2013-01-17 05:52:30 UTC
Have you updated vdsm on the RHS 2.0plus nodes with latest vdsm QA release?

Comment 3 Dustin Tsang 2013-01-17 14:18:48 UTC
I might not have the latest QA rpms for RHS 2.0plus. Closing as not a bug.