Bug 1140212 - vmware: Fix problems with VIM API retry logic
Summary: vmware: Fix problems with VIM API retry logic
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z1
: 5.0 (RHEL 6)
Assignee: Eric Harney
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On: 1102340 1140213
Blocks: 1055536 1140210
TreeView+ depends on / blocked
 
Reported: 2014-09-10 13:49 UTC by Scott Lewis
Modified: 2016-04-27 02:26 UTC (History)
8 users (show)

Fixed In Version: openstack-cinder-2014.1.2-3.el6ost
Doc Type: Bug Fix
Doc Text:
Previously, OpenStack Block Storage (cinder) would retry any vSphere API call which failed, not just those which failed due to authentication or temporary network issues. Additionally, the code to automatically recreate a session could fail spuriously under some circumstances. This meant that any vSphere API call that failed would be called multiple times, which increased the load on the vSphere server. Also, API failures could result in a failure to re- establish a new session, causing all subsequent API calls to fail. With this update, vSphere API calls are only retried for transient network or session errors, and session recreation is independently retried for connection errors. This reduces the load on the vSphere server, and sessions are reliably recreated if they expire or fail.
Clone Of: 1102340
Environment:
Last Closed: 2014-09-30 17:52:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1294598 0 None None None Never
Launchpad 1302514 0 None None None Never
OpenStack gerrit 95651 0 None None None Never
Red Hat Product Errata RHBA-2014:1343 0 normal SHIPPED_LIVE openstack-cinder bug fix advisory 2014-09-30 21:50:00 UTC

Comment 6 errata-xmlrpc 2014-09-30 17:52:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1343.html
Note You need to log in before you can comment on or make changes to this bug.