DELETE /v2/cache/{image_id} and /v2/cache returns HTTP 200 response
code to user but as per proposal it should be HTTP 204. This change
returns HTTP 204 response to user.
Closes-Bug: #1980049
Change-Id: I9d1c25638584fe346e3937d0536413d548d46e8e
Thread pool support in oslo.db was already deprecated[1], and it is not
actually used by Glance.
[1] 74c6bf266e0b86ceb4726cad9268f134d423bae8
Change-Id: I79e934f34f33953c821b6529a34e44dcf2a9688c
- qemu-img is provided by qemu-tools
- pg_config is provided by postgresql-server-devel
Closes-Bug: #1978869
Change-Id: Ia0e5f52f3841b3306a8776762d18a56c6df1e2f5
In Xena we have mangaed to move all policy checks to API layer,
now removing the dead code from policy and authorization layer
NOTE: Some of the code is still being used from policy layer,
hence keeping it there only at this moment.
Change-Id: Ibee749cde20687d8c243cf84ae80b4de67d8ef3d
This API version increment is due to change I6a875a38bef5, which
corrected the response code for the admin-only API call:
PUT /v2/cache/{image_id}
The call now returns 202 upon success (it had been returning 200).
The intent of this version bump is to get the attention of operators
to take note of this change; from now on, the call always returns 202
upon success regardless of what API version you request.
Additionally, cleaned up some version tests that had gotten out of
date and were not thoroughly testing version negotiation.
Also, corrected the version negotiation code around the v2.13 API.
The versions response had been modified by change I6882fd2381e6 to
only include v2.13 when the 'enabled_backends' config option had a
value, but the versions negotiation code was not updated to reflect
that.
Change-Id: I0cf35ed7e21497826cd581e59aa58774f030b9f6
Related-bug: #1971521
oslo.config 4.5.1 contains change I2e1f187feaf4, which makes
the workaround introduced by change Ic40f582f83e0 unnecessary.
Change-Id: Ib7fc2f2082981b1765e901ca5b277fce08221ba8
Related-bug: #1962581
Related-bug: #1962603
This reverts commit d7fa7a0321ea5a56ec130aa0bd346749459ccaf2.
Reason for revert: This is no longer needed as the devstack patch is merged to fix this issue https://review.opendev.org/c/openstack/devstack/+/841804
Change-Id: I214c9a6017f66d3eb6589496726e8c8f895d56aa
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Moving the py36 job to py38 based as well as
updating the python classifier also to reflect the same.
openstack-tox-functional-py36-fips job is left which can be moved
to py38|py39 based once that job is defined in openatck-zuul-jobs
repo.
openstack-tox-functional-py36-fips job will be migrated to py38 or py39
in followup patch as that need openstack-zuul-config changes too.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: Id0813d9dc553dd424732079039349b42f6f3201b
This reverts commit 025ba83c470fd58425273ad10975a1eb3d095452.
Reason for revert: This is no longer needed as the devstack patch is merged to fix this issue https://review.opendev.org/c/openstack/devstack/+/841804
Change-Id: Ie72a2531172208e32626ad2060737257663eba46
Creates Metadata def for CPU Mode. The allowed
modes are "none", "host-passthrough", "custom"
and "host-model".
Change-Id: Id7a01546334ddea952708143c5dfc7861353f2fc
Closes-Bug: 1636243
This commit adds three new flavor/image options to the interface.
The new options will allow the user to select and configure an
emulated virtual TPM in the guest. The new options are:
traits:COMPUTE_SECURITY_TPM_1_2
traits:COMPUTE_SECURITY_TPM_2_0
hw:tpm_model
nova blueprint: add-emulated-virtual-tpm
Change-Id: I1ff51f608b85dbb621814e70079ecfdd3d1a1d22
Signed-off-by: Paul-Emile Element <Paul-Emile.Element@windriver.com>
Signed-off-by: Chris Friesen <chris.friesen@windriver.com>
Some projects like cinder have dropped support for Python 3.6 and are
no longer compatible with CentOS Stream 8 which uses Python 3.6 as
the default runtime.
Change-Id: I48f88c188f830f61c03ec5570cd95731636a0396
Images for the aarch64 ARM architecture do have the architecture
property set to aarch64.
This is useful to know when trying to filter by properties like:
openstack image list --property architecture=aarch64
Change-Id: Ib4c0130bee302ee886521b74cf5434a0073cecf6
If a namespace is deleted by another client while we are doing a
namespace list operation, we will fail the list with NotFound if we
try to pull the resource_type_associations list. The latter re-queries
the DB for the namespace and will raise NotFound to us. This is
especially bad because the namespace being deleted need not even
belong to the caller of the list, as is the case in a tempest run.
This makes us catch the failure and continue the operation, reporting
no associations so that the client gets a consistent view and no
error.
Closes-Bug: #1973631
Change-Id: I09fc9164a08f42507d2aec44c5b382a72f232571
With change[1], we moved glance cinder jobs parent from
tempest-integrated-storage-import to regular
tempest-integrated-storage job but this job also has
import workflow enabled[2].
In this patch we are overriding GLANCE_USE_IMPORT_WORKFLOW
to False in cinder jobs to ensure that import workflow
is disabled in those jobs.
Also removing -import from job names since it's not using
import plugin anymore.
[1] https://review.opendev.org/c/openstack/glance/+/841548
[2] https://opendev.org/openstack/tempest/src/branch/master/zuul.d/integrated-gate.yaml#L195
Related-Bug: #1973136
Change-Id: I2775e007f942feed8fa6ae5e385c03992859edc1
This was already fixed in 4889dc1814185380d282ba13167b5f2eb3a4c0a9 but
we did not enforce this rule and reintroduced "bad" string
interpolations. This patch adds a hacking rule to prevent us from doing
this again in the future.
Change-Id: I96d9a157d3887286542859d67138ffdae5a589f1
Recently, glance-multistore-cinder-import job started failing.
As per the RCA done here[1], the reason is glance is using
import workflow to create images which is an async operation.
As in case of glance cinder configuration, there are a lot of
external APIs (cinder) called like volume create, attachment
create, attachment update, attachment delete etc which takes
time to process hence the image doesn't get available in the
expected time (as per devstack) hence the failure.
Disabling import workflow will cause the images to be created
synchronously which should pass the glance cinder jobs.
To disable import workflow, we are inheriting from
tempest-integrated-storage and not
tempest-integrated-storage-import (which has import plugin enabled).
[1] https://review.opendev.org/c/openstack/glance/+/841278/1#message-456096e48b28e5b866deb8bf53e9258ee08219a0
Closes-Bug: 1973136
Change-Id: I524dfeb05c078773aa77020d4a6a9991a7eb75c2
