Bug 1729812 - [HP3Par-8400] Instance creation failed.
Summary: [HP3Par-8400] Instance creation failed.
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
urgent
Target Milestone: ---
: ---
Assignee: Cinder Bugs List
QA Contact: Tzach Shefi
Chuck Copello
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-15 01:57 UTC by Nilesh
Modified: 2020-02-11 04:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Launchpad 1809249 None None None 2019-07-23 20:15:31 UTC

Comment 3 Alan Bishop 2019-07-16 19:40:09 UTC
Once again, the logs were not collected with DEBUG enabled. Please enable DEBUG and collect the cinder-volume logs.

My understanding is the os-brick package was a hotfix. Was the hotfix installed by customizing the cinder-volume container image on the director, followed by having the director deploying the hotfixed c-vol image? Or was the os-brick RPM patched into the running c-vol container? I ask because I'd like to confirm the c-vol process was restarted after the os-brick RPM was updated.

Comment 6 Alan Bishop 2019-07-23 20:15:31 UTC
The symptoms match a known problem with the 3par driver [1]. The LP bug
describes a situation where the FC zoning doesn't allow the controller to
access all target ports on the 3par backend, and the 3par driver happens
to pick a port that isn't accessible.

[1] https://bugs.launchpad.net/cinder/+bug/1809249

Per LP bug, a workaround is to set use_multipath_for_image_xfer=True, which 
will force the driver to scan all ports.

If setting use_multipath_for_image_xfer=True doesn't correct the problem, then
we may need to get HPE involved. If that's necessary, then please set
hpe3par_debug=True and capture more cinder-volume logs.


Note You need to log in before you can comment on or make changes to this bug.