In 48dd520958 support for the 2.0
consoleauth rpc API was added which missed the return statement in the
check_token method. Because of this all the components that had to
verify a token against consoleauth component would fail to do so.
This patch fixes the check_token method and extends the tests to cover
the new v2.0 class.
Closes-Bug: #1244220
Change-Id: I4e5186943d28609083f723f4b43ab6f0ecbffd27
We no longer use LazyPluggable for the db_backend, and
dbapi_use_tpool options. These now come from
nova.openstack.common.db.api.
Also, removed doc about enable_new_services which seemed a bit
lonely without the rest and probably isn't needed since the
config option help explains it well enough.
Change-Id: I14d00e013a1a0c0dfc80e0bba8ad82e97940d6ac
The following operations would fail due to invalid references, either by name
or UUID:
- resize
- resize-confirm
- resize-revert
Closes-bug: #1199954
Change-Id: I39b804ed3c0c57455547d9ece0ef779cf73a5926
Ensure that the correct UUID's are reported to the compute
manager. The fix will return only valid UUID's and not all
of the names of the instances running.
Closes-Bug: #1237795
Change-Id: I32bb6f4783dcc80697abebd5a7f45ef9950a0896
While in a child cell, do not raise when the current flavor is passed
into compute API's resize(). This is behavior that should be limited to
nova-api.
Closes-bug: 1243816
Change-Id: Ie67af3ab3003164e9742a8c4d5bd75502dca96c4
Resizing to same flavor for compute cells should not fail, so this patch
reworks the current test such that it'll be easier to modify when the
compute cells bug is fixed in an upcoming patch.
Change-Id: I4331db8636c2256f18cd0a2196033e1a2257c971
They are actually testing resize because of 'flavor_id_passed' being
passed in as True to _test_resize(), when that is already the default
for testing resize.
Change-Id: Iae31dad8e869481898579b5cd752e8e5baa306d1
The builtin basestring abstract type was removed in python3,
use str instead, we need to using six.string_types to replace
the basestring for python3 compatibility.
Partial Implements bp basestring-py3-compatible
Change-Id: I719e104ae46ebb6e986c53a019b93e3a45e6d0fd
libvirt driver's get_connection is not thread safe in the
presence of a libvirtd restart during concurrent incoming
requests.
With existing code each will in turn call get_connection,
find the connection is broken, try to create new one, block
for a while and yield to the next thread to do the same.
You get as many connections as there are incoming requests
and only the last one is used finally. If enough are incoming
these connections can exhaust the client pool configured
for libvirtd.
One fix is to hold a lock while creating the connection.
Note that has_min_version calls _conn which calls get_connection
and thus the direct call to _has_min_version()
Also added the exception text if it fails to register an event
handler for lifecycle events.
Change-Id: I090765802bfe443440f16722bc7c43b6280fe56a
Fixes: bug #1240905