Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1347441

Summary: vnx driver takes too long to acquire lock
Product: Red Hat OpenStack Reporter: Jack Waterworth <jwaterwo>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: bschmaus, eharney, geguileo, jwaterwo, scohen, srevivo, tshefi
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-21 14:53:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jack Waterworth 2016-06-16 21:28:26 UTC
Description of problem:

vnx driver takes too long to acquire lock. in the below example, it takes 80 seconds to acquire the lock, which breaches the default rpc timeout in cinder by 20 seconds.  this leads to a failure being reported by cinder-api.

2016-05-13 19:34:32.440 52360 DEBUG oslo_concurrency.lockutils [req-7ae36a65-9337-42f8-a49d-c00265200368 ef2aeb1058774b8f993a8cac1bebc55e d85cc4f346614a09b512c29a70cb10ce - - -] Lock "emc-connection-slnec1cmp4.localdomain" acquired by "do_terminate_connection" :: waited 80.522s inner /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:444


Version-Release number of selected component (if applicable):
python-cinder-2015.1.2-5.el7ost.noarch

How reproducible:
Every time by customer

Steps to Reproduce:
1. Deploy overcloud
2. Create instances with cinder attached volumes on overcloud
3. Run stack-delete from undercloud

Actual results:
stack-delete fails due to 500 response from cinder-api during nova detach.

Expected results:
stack-delete should complete without failure

Comment 6 Sean Cohen 2016-07-07 12:46:11 UTC
Any progress with this case?
Thanks,
Sean

Comment 8 Gorka Eguileor 2016-07-21 14:53:30 UTC

*** This bug has been marked as a duplicate of bug 1351169 ***