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

Bug 1542438

Summary: HPE3PAR: Create FC vlun as host sees
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: Avi Avraham <aavraham>
Severity: high Docs Contact: Kim Nylander <knylande>
Priority: high    
Version: 11.0 (Ocata)CC: geguileo, jraju, srevivo, tshefi
Target Milestone: z5Keywords: OtherQA, Triaged, ZStream
Target Release: 11.0 (Ocata)Flags: tshefi: automate_bug-
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-cinder-10.0.6-18.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-18 16:48: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 Jaison Raju 2018-02-06 11:14:48 UTC
Description of problem:
hp 3par StorageAPI provides response without remoteName & cinder volume reports:
 u"VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Driver initialize connection failed (error: 'remoteName').\n"]. None
This task was done by initialize_connection . 
Due to this failure volume attach fails.
This is reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1517888

HP has suggest the following fix for this issue: https://review.openstack.org/#/c/525719/



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

How reproducible:
Always on customer end.

Steps to Reproduce:
1.
2.
3.

Actual results:
volume attach fails with cinder hp 3par plugin failing to find 'remoteNmae' .

Expected results:


Additional info:
I will raise another bz for backporting this to RHOS10 .

Comment 7 Tzach Shefi 2018-05-07 06:49:25 UTC
A HPE3par driver issue, as we don't have access to such HW,
Setting OtherQA as well as no QE automation/coverage.

Comment 10 errata-xmlrpc 2018-05-18 16:48: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-2018:1611