Bug 1226186 - In Create Brick Scenario VG Create failed in first time
Summary: In Create Brick Scenario VG Create failed in first time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHGS 3.1.0
Assignee: Timothy Asir
QA Contact: Timothy Asir
URL:
Whiteboard:
Depends On: 1198568 1206526
Blocks: 1202842 1224288
TreeView+ depends on / blocked
 
Reported: 2015-05-29 07:36 UTC by Timothy Asir
Modified: 2015-07-29 05:31 UTC (History)
9 users (show)

Fixed In Version: rhsc-3.1.0-59, vdsm-4.16.20-1.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-29 05:31:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1494 0 normal SHIPPED_LIVE Red Hat Gluster Storage Console 3.1 Enhancement and bug fixes 2015-07-29 09:24:02 UTC
oVirt gerrit 41392 0 master MERGED gluster: fix vg create failed first time during brick create Never
oVirt gerrit 42363 0 ovirt-3.5-gluster MERGED gluster: fix vg create failed first time during brick create Never

Description Timothy Asir 2015-05-29 07:36:56 UTC
Description of problem:
VG Create failed first time on a given device

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

How reproducible:
frequently

Steps to Reproduce:
Execute create brick scenario on a new device


Actual Results:
VG Create failed first time frequently in a device.


Additional info:

VDSM Log message:
Thread-15::ERROR::2015-05-29 13:01:02,697::BindingXMLRPC::1176::vds::(wrapper) unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/rpc/BindingXMLRPC.py", line 1160, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/gluster/api.py", line 62, in wrapper
    rv = func(*args, **kwargs)
  File "/usr/share/vdsm/gluster/api.py", line 594, in createBrick
    raidParams)
  File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>
    **kwargs)
  File "<string>", line 2, in glusterCreateBrick
  File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod
    raise convert_to_error(kind, result)
ValueError: member has wrong format
periodic.Scheduler::DEBUG::2015-05-29 13:01:04,241::periodic::185::periodic.Operation::(_step) after 2.000000 seconds: VmDispatcher(<class 'virt.periodic.DriveWatermarkMonitor'>)

Comment 2 Timothy Asir 2015-05-29 07:47:52 UTC
Currently we are using vdsm lvm module for pv create and
blivet to create vg. This issue is not identified if we
use blivet for creating both pv and vg.
But blivet has few issues while creating a vg. Its able
to create pesize as minimum 1mb currently.
So I sent a workaround to fix the issue
patch: https://gerrit.ovirt.org/#/c/41392/ 

As the vdsm lvm module vg create has few issues,
I used lvm vgcreate command to create the vg
in the workaround patch.

Comment 3 Timothy Asir 2015-05-29 07:56:17 UTC
It depends on the following blivet bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1206526
https://bugzilla.redhat.com/show_bug.cgi?id=1198568
The above blivet bugs for create a vg with any given
pe size in power of 2 (lvm2 limitation)

Currently the fixes are in On_QA and its not available
in any channel right now, Once its available for every os
i will send a patch to use blivet to create pv and vg.
Till then we will use the lvm vg create command
as a workaround.

Comment 5 Timothy Asir 2015-06-13 18:29:31 UTC
Patch sent to upstream: https://gerrit.ovirt.org/#/c/41392/

Comment 6 Ramesh N 2015-06-14 07:50:57 UTC
I am not able to reproduce this issue consistently. Give the steps to re-produce.

Comment 7 RamaKasturi 2015-06-19 09:01:53 UTC
Hi Tim,

   I have not hit this issue any time till now. Since you hit this issue it would be good if you can verify this bug.

Thanks
kasturi

Comment 8 Timothy Asir 2015-06-29 09:57:06 UTC
Tested in Fedora and RHEL6 and RHEL7. Its working fine.

Comment 9 errata-xmlrpc 2015-07-29 05:31:11 UTC
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.

https://rhn.redhat.com/errata/RHEA-2015-1494.html


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