a229faf8ba
Concurrent VIM API invocations after session expiration would result in concurrent login attempts. In such cases, if a login attempt is made after a successful one, it would result in InvalidLogin. This is because vCenter server won't allow login within an active session. On the other hand, if two or more login attempts reach vCenter at the same, it would result in session leak-- the last one returned overwrite any of the previous sessions. This patch prevents the race condition by making session creation synchronized and checking for an active session before login attempt. We can also remove the call to terminate previous session after login since a login is attempted only if there is no active session. Change-Id: Ib4ca3553ce14c80ab722092907d797767072741c Closes-Bug: #1409014
28 lines
597 B
Plaintext
28 lines
597 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr>=0.6,!=0.7,<1.0
|
|
|
|
stevedore>=1.1.0 # Apache-2.0
|
|
netaddr>=0.7.12
|
|
|
|
# for timeutils
|
|
iso8601>=0.1.9
|
|
|
|
# for jsonutils
|
|
six>=1.7.0
|
|
|
|
oslo.i18n>=1.0.0 # Apache-2.0
|
|
oslo.utils>=1.1.0 # Apache-2.0
|
|
Babel>=1.3
|
|
|
|
# for the routing notifier
|
|
PyYAML>=3.1.0
|
|
|
|
suds>=0.4
|
|
eventlet>=0.15.2
|
|
requests>=2.2.0,!=2.4.0
|
|
urllib3>=1.8.3
|
|
oslo.concurrency>=0.3.0,!=0.4.0 # Apache-2.0
|