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.
Reviewed: https:/ /review. opendev. org/657585 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=b7c81a7b426 136314fb12f5aaf cb977b25d49cc6
Committed: https:/
Submitter: Zuul
Branch: master
commit b7c81a7b4261363 14fb12f5aafcb97 7b25d49cc6
Author: raghavendrat <email address hidden>
Date: Tue May 7 05:30:48 2019 -0700
3PAR: Provide new option to specify NSP for single path attachments
This fix aims to resolve below mentioned bugs: /bugs.launchpad .net/os- brick/+ bug/1812665 /bugs.launchpad .net/cinder/ +bug/1809249 /bugs.launchpad .net/cinder/ +bug/1734917
https:/
https:/
https:/
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.
Change-Id: If77d384afbc709 7ed55a03e9b4bc7 f8e1966a5c5
Closes bug: #1809249