Red Hat Bugzilla – Bug 970759
[RHSC] Creating Striped-Replicate Volume via Gluster does not sync with RHSC
Last modified: 2013-09-23 18:25:43 EDT
Created attachment 756938 [details]
Volume Crteate Sync
Description of problem:
While testing Volume Create syncing with RHSC, the following volume when created via gluster did not sync with RHSC:
volume create demo-striped-replicate stripe 2 replica 2 10.8.30.25:/demo/stripedReplicateBrick1 10.8.30.25:/demo/stripedReplicateBrick2 10.8.30.26:/demo/stripedReplicateBrick1 10.8.30.26:/demo/stripedReplicateBrick2 force
Gluster volume info command shows the following:
Volume Name: demo-striped-replicate
Volume ID: e5062b05-94b8-45fc-9af8-c60a3e4ba1b5
Number of Bricks: 1 x 2 x 2 = 4
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Volume should have synced with RHSC
From logs -
2013-06-04 14:52:01,075 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler_Worker-32) Error while refreshing Gluster lightweight data of cluster Matts_Cluster!: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: java.lang.IllegalArgumentException: No enum constant org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeType.STRIPED_REPLICATE (Failed with VDSM error ENGINE and code 5001)
at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:127) [bll.jar:]
Changing priority as STRIPED_REPLICATE volume type is not supported in RHS
Verified as fixed in Red Hat Storage Console Version: 2.1.0-0.bb5.el6rhs. Striped-replicate volume created from gluster CLI now syncing with engine.
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.