Bug 1768832

Summary:	3PAR driver picks wrong port when not in multipath mode
Product:	Red Hat OpenStack	Reporter:	Pablo Caruana <pcaruana>
Component:	openstack-cinder	Assignee:	Pablo Caruana <pcaruana>
Status:	CLOSED ERRATA	QA Contact:	Tzach Shefi <tshefi>
Severity:	medium	Docs Contact:	Chuck Copello <ccopello>
Priority:	medium
Version:	13.0 (Queens)	CC:	ccopello, ndeevy, pcaruana, tberry, tenobreg, tshefi
Target Milestone:	---	Keywords:	OtherQA, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-cinder-12.0.10-1.el7ost	Doc Type:	Bug Fix
Doc Text:	Before this update, zone creation that used a second or later target nsp from a 3PAR back end caused the creation of bootable volumes to fail intermittently. This is because the HPE 3PAR client code used the first target nsp to form the initiator target map, in the case of a system that was connected to HPE 3PAR via FC with multipath disabled. With this update, you can specify the target nsp in the 3PAR backend section of the `cinder.conf` file in the following way: hpe3par_target_nsp = <n:s:p> This means that the target information comes from `cinder.conf`, the initiator target map is created from the respective wwn information, and the creation of bootable volumes is successful.	Story Points:	---
Clone Of:	1768790	Environment:
Last Closed:	2020-03-10 11:25:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1768790
Bug Blocks:

Description Pablo Caruana 2019-11-05 10:35:56 UTC

+++ This bug was initially created as a clone of Bug #1768790 +++

+++ This bug was initially created as a clone of Bug #1667922 +++

3PAR: Add config for NSP single path attach

This fix aims to resolve below mentioned bugs:
https://bugs.launchpad.net/os-brick/+bug/1812665
https://bugs.launchpad.net/cinder/+bug/1809249
https://bugs.launchpad.net/cinder/+bug/1734917

Given a system connected to HPE 3PAR via FC and multipath is disabled.
When user tries to create bootable volume, it fails intermittently
with following error:

    Fibre Channel volume device not found

This happens when a zone is created using second or later target nsp
from 3PAR backend. In this case, HPE 3PAR client code picks up first
target nsp to form initiator target map.

To avoid above mentioned failure, user can specify target nsp in 3PAR
backend section of cinder.conf as follows:

    hpe3par_target_nsp = <n:s:p>

This target information is read from cinder.conf and respective
wwn information is fetched. Later initiator target map is created
using wwn information and bootable volume is created successfully.

--- Additional comment from Pablo Caruana on 2019-11-05 10:09:12 UTC ---

Comment 7 errata-xmlrpc 2020-03-10 11:25:28 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-2020:0764