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
Added OtherQA, don't have access to such a storage for testing.
@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.
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