b7c81a7b42
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. Change-Id: If77d384afbc7097ed55a03e9b4bc7f8e1966a5c5 Closes bug: #1809249