Bug 1200909 - Volume creation with BD xlator missing existing VG
Summary: Volume creation with BD xlator missing existing VG
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: qemu-block
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-11 15:52 UTC by sir.fre
Modified: 2018-11-19 08:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 08:33:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description sir.fre 2015-03-11 15:52:43 UTC
Description of problem:
* While trying to create Bricks & volumes on Gluster, whichever node you are on:
gluster volume create bdVolume1 gluster1:/storage/disk1/bdmeta?gluVolG force

Gluster refuses to create any brick on the vg/lv. It states that the vg could 
not be found, while it's clearly visible & usable with pvs, vgs and lvs.


Version-Release number of selected component (if applicable):
* RHEL 7.1
* Gluster 3.5.3

How reproducible:
-

Steps to Reproduce:
1. pvcreate on a disc
2. vgcreate gluVolG /dev/disc
3. create necessary dir /storage/disk1/bdmeta
4. validated all steps before ;)
5. create brick/volume

Actual results:
Volume create: bdVolume1: failed: no such vg: gluVolG
or
Volume create: .... failed: Staging failed on ... Error: no such vg: ... 


Expected results:
Volume creation

Comment 2 sir.fre 2015-03-11 17:08:41 UTC
Updated gluster 3.5.3 to 3.6.2-1.el7 as required by other RHEL7-pkgs like QEMU-stuff.

Still same issue.

Comment 3 SATHEESARAN 2015-03-12 06:51:59 UTC
Red Hat Storage doesn't supports BD Xlator.
Also I see that the glusterfs version used was, 3.5.3 & 3.6.2-1.el7, which is the upstream builds.

This bug should ideally belong to upstream and not downstream.
Making changes accordingly.

Comment 4 Kaushal 2016-08-30 12:56:03 UTC
GlusterFS-3.6 is nearing its End-Of-Life, only important security bugs still make a chance on getting fixed. Moving this to the mainline 'version'. If this needs to get fixed in 3.7 or 3.8 this bug should get cloned.

Comment 5 Vijay Bellur 2018-11-19 08:33:51 UTC
Thank you for your report. bd translator is not being maintained actively and hence this bug is being closed.


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