Modified the "Checksum" description as mentioned , it is not computed from
victoria release .
Closes-Bug: #1875629
Change-Id: Id4299c7e02298157ad88971a78fac72a9f0248d0
Glance yoga release notes generates one warning and as a result
it will fail to list it on release page [1] like it is
showing for Xena release.
The warning in the test log is;
"The Fixes section of
releasenotes/notes/fix-md-tag-create-multiple-c04756cf5155983d.yaml is
not a recognized section. It should be one of: features, issues,
upgrade, deprecations, critical, security, fixes, other. This
will be an error in a future release."
Rmoved the "Fixes" section from mentioned release note as it is already
included in `yoga-rc1-release-notes-153932161f52a038.yaml`.
[1] https://releases.openstack.org/teams/glance.html#team-yoga-glance
Closes-Bug: #1963282
Change-Id: I0167cd65f37fc744aa686c626739f9563054666c
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: Ida380f2352455955eb84a50916653560d232b544
The default value is being set too early. We don't want to use
the value of sys.executable at the time the config is generated,
because that's unlikely to map to an existing interpreter in an
actual deployment.
Change-Id: Ic40f582f83e04c6915a3fcb231d6d95ca071c100
Closes-bug: #1962581
This patch adds a new API to glance ``GET /v2/info/stores/detail``
to expose the stores specific details about the store like store
type and other specific store properties.This operation
will be admin only and validated by the new policy rule
``stores_info_detail`` which defaults to admin only
Implements: blueprint expose-store-specific-info
Change-Id: I6882fd2381e6ae245fd8c61bf9f4d52df2b216f5
It was observed that md-tag-create-multiple
(/v2/metadefs/namespaces/{namespace_name}/tags) API overwrites
existing tags for specified namespace rather than creating new one
in addition to the existing tags.
This patch resolves the issue by introducing a header 'X-Openstack-Append'
which on being True will append the new tags to existing ones and
if False will continue to overwrite the tags.
Implements: blueprint append-tags
Closes-Bug: #1939169
Change-Id: I29448746b14c542e5fbf0283011968ae1516642e
Temporarily make the FIPS job non-voting till we figure out why
its failing. Restore the non-fips version of the cinder job so
we keep the coverage.
Change-Id: I1a9dbd087cca52798f0d01c62ebb47e37f52d87a
Update the data migration current release to 'yoga'. Include a
semver pseudo-header in this commit message so that pbr will
increment the major version number, otherwise
glance.tests.unit.gate.test_data_migration_version will break.
Also add a reminder about this to the release cycle tasks list.
Change-Id: Ibdbeb752d29afeb48628587442577ab139be9ac9
Sem-Ver: api-break
Python 2 support was removed during Ussuri cycle. This change adds
the classifier to clearly state that only Python 3 is supported.
Change-Id: Ib244469e09e396ea897d1778bb1bad15cebf1f10
Some jobs have been modified to run to confirm that functionality is
still working when FIPS is enabled on the nodes.
As the FIPS tests currently run on centos nodes, code is added
to the test-setup script to set up the databases correctly. Also had
to increase the swap space on the nodes; see [0] for an explanation.
The current FIPS jobs run using python 3.6 on centos-8-stream. We will
modify these to run on centos-9-stream and python 3.9 in a
subsequent patch.
[0] https://review.opendev.org/c/openstack/devstack/+/803706
Change-Id: I060d8247c7b09f63990ea411e6c6a056bb50410d
This adds a /v2/info/usage API endpoint which exposes to the user
their current limits and usage.
The discovery API does not (appear to) have existing tests, so this
adds a module for that, although only usage tests are added currently.
Implements: blueprint quota-api
Change-Id: I50c98bac50f815bdb9baae024e77afd388f74554
In set_property_atomic() we pass an integer query filter for the
deleted field, since most projects use an integer for this column.
However, in glance the column is a boolean, which trips up postgres
since the types are different (mysql and sqlite work fine). This
minor change to use False instead of 0 should fix that for postgres
users.
Change-Id: I5149df76943c1c19f3204b904c0e2d3ef846bdf7
Closes-Bug: #1953063
This is available on all supported Python versions.
Change-Id: I76a696e56e04ec47b107af8e169c04138cf45fbb
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
There's nothing unusual about this anymore. Python 2 is no longer
supported and Python 3 is the default.
Change-Id: I8cc52a363f75bbcb89699ec65e02ac1c68d772ee
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
These don't do anything in Python 3. We should use '__str__' instead.
Change-Id: I3c06744a1de4a65b97556665040bcaa347cdb76b
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This is no longer necessary now that everything is a unicode string.
Change-Id: I809d9ba93ed19a8dd7a7be59e5470c56aca871e7
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
We also update docs since guidance has necessarily changed here.
Change-Id: I7c24a1aa3545f3499a7a2ce30b73e2656666c764
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This is a rather beefy change due to the number of usages of this
import. The changes are trivial though.
Change-Id: I7badeeaca438b0291f4ed86670e7f217e6372c61
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
This is the same as the 'range' keyword in Python 3
Change-Id: If3aa008522c24e870b7bf13de32b8ed1b27cb519
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
