Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1238554

Summary: libstoragemgmt: Can't create RAID device using megaraid plugin
Product: Red Hat Enterprise Linux 7 Reporter: Bruno Goncalves <bgoncalv>
Component: libstoragemgmtAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Bruno Goncalves <bgoncalv>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: tasleson
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:46:19 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:

Description Bruno Goncalves 2015-07-02 07:07:31 UTC
Description of problem:
Trying to create a RAID device using MegaRaid plugin fails:

INVALID_ARGUMENT(101): Illegal input disks argument: disks are not from the same controller/system. 

Version-Release number of selected component (if applicable):
libstoragemgmt-megaraid-plugin-1.2.3-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.List the controllers
# lsmcli -u megaraid:// list --type systems 

2.List the disks from the controller
lsmcli -u megaraid:// list --type disks --sys <SYSTEM_ID>

3. Try to create a RAID1 device using 2 disks
# lsmcli -u megaraid:// volume-raid-create --name lsm_test --disk <DISK1_ID> --disk <DISK2_ID> --raid-type RAID1 --sys <SYSTEM_ID>
 

Actual results:
INVALID_ARGUMENT(101): Illegal input disks argument: disks are not from the same controller/system.

Expected results:
RAID device should be created

Additional info:
The server has 2 controllers, I tried to create RAID device on second one.

Comment 2 Gris Ge 2015-07-02 07:38:02 UTC
Patch posted to upstream https://github.com/libstorage/libstoragemgmt/pull/34

Comment 4 Bruno Goncalves 2015-09-02 08:14:38 UTC
Verified on libstoragemgmt-1.2.3-3.el7.


# lsmcli -u megaraid:// volume-raid-create --name lsm_test --disk S0K243HH0000B434AASH --disk S0K41ADE0000M535HD0G --raid-type RAID1 --sys SV32402879
ID             | Name           | SCSI VPD 0x83 | Size         | Disabled | Pool ID        | System ID 
-------------------------------------------------------------------------------------------------------
SV32402879:VD0 | VD 0: lsm_test |               | 299439751168 | No       | SV32402879:DG0 | SV32402879

Comment 6 errata-xmlrpc 2015-11-19 11:46:19 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-2342.html