9e122f1166
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: I2da5d4a0334f07967af5ff7aaa39a0ecc4b12204 Closes-bug: #1809249 Closes-bug: #1812665 Closes-bug: #1734917
8 lines
276 B
YAML
8 lines
276 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug 1809249 <https://bugs.launchpad.net/cinder/+bug/1809249>`_ -
|
|
3PAR driver adds the config option `hpe3par_target_nsp` that can be
|
|
set to the 3PAR backend to use when multipath is not enabled and
|
|
the Fibre Channel Zone Manager is not used.
|