Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1230252 - [New] - Creating a brick using RAID6 on RHEL7 gives unexpected exception
[New] - Creating a brick using RAID6 on RHEL7 gives unexpected exception
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: vdsm (Show other bugs)
3.1
Unspecified Unspecified
high Severity high
: ---
: RHGS 3.1.0
Assigned To: Timothy Asir
RamaKasturi
:
Depends On:
Blocks: 1202842
  Show dependency treegraph
 
Reported: 2015-06-10 09:48 EDT by RamaKasturi
Modified: 2015-07-29 01:01 EDT (History)
7 users (show)

See Also:
Fixed In Version: vdsm-4.16.20-1.1.el6rhs.x86_64.rpmv
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 01:01:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 41392 None None None Never
Red Hat Product Errata RHEA-2015:1494 normal SHIPPED_LIVE Red Hat Gluster Storage Console 3.1 Enhancement and bug fixes 2015-07-29 05:24:02 EDT
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description RamaKasturi 2015-06-10 09:48:34 EDT
Description of problem:
while trying to create a brick using RAID6 device on RHEL7.1 gives unexpected exception.

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.58.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Add a host with RAID6 device.
2. Try creating a brick by selecting the RAID Type as RAID6,stripe size as 128kB and no.of disks as 12.
3. click on 'ok'

Actual results:
Fails to create a brick and throws unexpected exception

Expected results:
Create brick should be successful.

Additional info:
Comment 2 RamaKasturi 2015-06-10 09:52:10 EDT
logs are attached in the link below.

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/rhsc/1230252/
Comment 3 Timothy Asir 2015-06-10 13:23:13 EDT
This version of blivet expects the minimum physicalextentsize of 1mb.
This issues is already fixed and available in the latest blivet version
(which is available in rhel 7.2 candidate)

For rhel7.1 i have already sent an workaround patch to upstream.
The workaround uses lvm command instead of using blivet vgcreate api.
Its still under review: https://gerrit.ovirt.org/#/c/41392/
Comment 5 Timothy Asir 2015-06-13 14:28:24 EDT
Patch sent to upstream: https://gerrit.ovirt.org/#/c/41392/
Comment 6 Timothy Asir 2015-06-15 08:46:24 EDT
its failed because the available python-blivet expects physicalextentsize should be > 1mb.

  File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
    raise convert_to_error(kind, result)
DeviceCreateError: ('vgcreate failed for vg-brick1: running lvm vgcreate -s 0m vg-brick1 /dev/sdb1 --config  devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] }  failed', u'vg-brick1')

Its fixed in the latest python-blivet version.
Comment 7 RamaKasturi 2015-06-19 08:17:29 EDT
Verified and works fine with build vdsm-4.16.20-1.1.el7rhgs.x86_64.

Python-blivet version:
-----------------------
python-blivet-0.61.0.26-1.el7.noarch

lvm version:
-----------------------
[root@rhs-arch-srv1 ~]# rpm -qa | grep lvm
lvm2-2.02.115-3.el7.x86_64
lvm2-libs-2.02.115-3.el7.x86_64


Kernel:
----------------------
 uname -a
Linux rhs-arch-srv1.lab.eng.blr.redhat.com 3.10.0-229.4.2.el7.x86_64 #1 SMP Fri Apr 24 15:26:38 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux

Able to create a brick using RAID6 on RHEL7. No exception is seen.
Comment 8 errata-xmlrpc 2015-07-29 01:01:21 EDT
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/RHSA-2015-1495.html

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