Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1676603

Summary: Support for HPE MSA2050 in Queens.
Product: Red Hat OpenStack Reporter: Siggy Sigwald <ssigwald>
Component: openstack-cinderAssignee: Sofia Enriquez <senrique>
Status: CLOSED ERRATA QA Contact: Tzach Shefi <tshefi>
Severity: high Docs Contact: Tana <tberry>
Priority: medium    
Version: 13.0 (Queens)CC: abishop, adakopou, amcleod, brian.rosmaita, chris.maio, eharney, fwissing, pgrist, senrique
Target Milestone: z6Keywords: OtherQA, Triaged, ZStream
Target Release: 13.0 (Queens)Flags: tshefi: automate_bug-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-cinder-12.0.4-9.el7ost Doc Type: Bug Fix
Doc Text:
Previously, when authenticating, a string match was performed on the `response-type` string. Performance with this mechanism was not consistent. With this update, authentication to the array uses the `response-type-numeric` value to determine success, rather than doing a string match against the `response-type` string.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-30 17:21:49 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 Siggy Sigwald 2019-02-12 16:30:04 UTC
Description of problem:
According to upstream docuemtation, the driver shipped with OSP13 seems to lack support for HPE MSA2050 as stated here[1]. However, there's support for it in Rocky[2] and Stein[3]. Customer would like to request support to be added for this storage to Queens (RHOSP13.

[1]https://docs.openstack.org/cinder/queens/configuration/block-storage/drivers/hp-msa-driver.html
[2]https://docs.openstack.org/cinder/rocky/configuration/block-storage/drivers/hp-msa-driver.html
[3]https://docs.openstack.org/cinder/latest/configuration/block-storage/drivers/hp-msa-driver.html

Comment 3 Tzach Shefi 2019-02-13 14:17:33 UTC
Added OtherQA, don't have access to such a storage for testing.

Comment 5 Alan Bishop 2019-02-13 16:00:05 UTC
@Siggy, thanks for the info in comment #1! This has quickly morphed into a relatively simple backport request. The upstream patch that fixes the driver initialization error has already merged, and upstream backports are already underway.

While it's great the patch allows the driver to come up, bear in mind HPE still needs to get the driver certified for OSP.

@Sofia, I'm not sure if the upstream author will submit their patch to stable/queens, so you may have to track that before backporting downstream.

Comment 28 errata-xmlrpc 2019-04-30 17:21:49 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://access.redhat.com/errata/RHBA-2019:0929