This commit does the following changes in gate testing:
- Test tempest-integrated-compute-rbac-old-defaults (Test the
RBAC old defaults which are deprecated but still supported)
in periodic weekly pipeline instead of check/gate pipeline.
Reason: Old defaults are deprecated and it will be rare to
have any changes in those. These should be ok to run weekly
to know if anything is broken for old defaults.
- Remove tempest-integrated-compute-enforce-scope-new-defaults
This test the new defaults which are enabled by default and
tested in every job.
Reason: We kept this job for cinder because their new defaults
are not enabled by default. To test nova new defaults combination
with cinder new defaults, we have Tempest job running in tempest
gate (tempest-full-enforce-scope-new-defaults).
Change-Id: I3a1634ff71b39c722401dea8e77092228f9cc064
When unprovision works via Ironic, all operations in _cleanup_deploy
have already been completed. Previous to this patch, we continue
attempting all the clean up steps, which eventually errors out with
BadRequest, or similar, and we complete the delete.
Howerver, if cleaning has started, we hit a conflict exception,
so we don't hit the expected error above.
Prior to moving to the SDK, that landed in Caracal,
we would retry on conflict errors. You can tweak the
config to keep retrying for the length of time cleaning
usually takes in your enviroment.
After this patch:
Ieda5636a5e80ea4af25db2e90be241869759e30c
We now hard fail with this error:
openstack.exceptions.ConflictException:
Failed to detach VIF xxx from bare metal node yyy
...
Node yyy is locked by host zzz,
please retry after the current operation is completed.
This change simply skips calling the operations that
will always error out, avoiding the need to wait for
cleainging to complete before getting the expected
error message.
Closes-Bug: #2019977
Related-Bug: #1815799
Change-Id: I60971b58cf1f24bdb5d40f668e380ebfee2ac495
_api_version was always being set to '2.1' so logic based on this wasn't
doing anything. Removing this also highlights a few other places where
we have useless variable assignment and mocking happening.
Change-Id: I4171191624e10513cbf094a3bebb4b1fcba3cc6c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
As with expected_errors previously, this will allow us to get rid of the
duplicate function definitions that are the bane of my life as I add
schemas.
Change-Id: I6df7b257f7d2460b053a62f4393021d17789ea05
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This will allow us to get rid of the duplicate function definitions that
are the bane of my life as we add schemas.
Change-Id: I1fbcb5dec81bcd66a863155783de6273e806dc2c
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Commit 14b5232e12 dropped use of
pkg_resources but also completely removed the __init__.py from
the nova.virt directory. This creates mayhem downstream in
distros where tooling considers this not a module and excludes it
from the installed package.
Restore the __init__.py to resolve this.
Change-Id: I40ee77ee3a41e1ff458c963f6609c03a5c69eb86
This new class is an unit test class for the server view builder
v2.96, which reproduces the bug #2095364. The bug is the list
server API and the list server details API returns 500 Internal
Server Error if request_spec object is missing by any reason.
Related-Bug: #2095364
Change-Id: I80d06ea335dd6fb311c4b9c9a79dbaa46ebe695f
This is similar to change I668643c836d46a25df46d4c99a973af5e50a39db
where the objects returned in a list from a libvirt call were not
tpool.Proxy wrapped. Because the objects are not wrapped, calling
methods on them such as listCaps() can block all other greenthreads
and can cause nova-compute to freeze for hours in certain scenarios.
This adds the same wrapping to libvirt calls which return lists of
virNodeDevice.
Closes-Bug: #2091033
Change-Id: I60d6f04d374e9ede5895a43b7a75e955b0fea3c5
Neutron networking backends today are expected to work without
the periodic healing of the cache in Nova. Turn it off to gain
additional performance and in order to start testing this
setup in advance, before we are ready to change the default
value to it.
Change-Id: Ic90949cae840290dc376af7a7a3056babe2539f2
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
This reverts commit 0fccb365dd.
Reason for revert: the current version does not have test coverage to assert the proxy is used so we should revert this and fix it before backporting
Change-Id: I51cf7da85e05131da72acdcf9be09121a326d414
This is not admin-only as suggested by the api-ref. In addition, there is
no mechanism available to disable flavors so this will always be false.
Change-Id: Ie1906366c8f141c6f6c58f21b0ff67eb827df4c8
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
The official service type for Cinder according to [0] is
"block-storage", so it should be allowed in the validation regex.
[0] https://specs.openstack.org/openstack/service-types-authority/
Closes-Bug: 2092194
Change-Id: I9a57aa72cc9589cec08b0f8d5797108043747ef6
Improve the schemas as suggested by stephenfin.
Manila is the OpenStack Shared Filesystems service.
These series of patches implement changes required in Nova to allow
the shares provided by Manila to be associated with and attached to
instances using virtiofs.
Implements: blueprint libvirt-virtiofs-attach-manila-shares
Change-Id: I0857410482439406da28410a6d7f5ca7f04e9c21
Vasyl Saienko