Heat dropped support for Python2 long ago,
and python2 is not even available on some newer platforms,
breaking installation of heat dependencies.
Change-Id: I37cf23a71202396bd28cd780455f6278b42c6e4b
Because change I7d1017bcd7147329c4e187336daee1a1ae280fa9 was backported
to the previous stable branch.
Change-Id: I2de594258231e3f1c217904afce88a83a8f94df3
This removes the experimental TripleO job. The job has been kept in
experimental queue and it has never attracted actual attention.
Also the job does not use the proposed change in heat but the current
master instead, so it's not useful to be in the Heat jobs.
Change-Id: I1b99f8d039271bff8e64d64ad5482231bf2a2118
This change adds validation of the limit query parameter in List
Software Config API, as was implemented for List Stack API, to avoid
internal error at database query.
story: 2009707
task: 44054
Change-Id: Ib57919faebbd4eb6aa13857e242eb5f3dc448a02
In some cases, some resources may require more than
one service_extension. In this case, we should allow
resources to define a list of required resources.
Change-Id: Iee0104a741cc050047824d23b8ab5ee9871c4f28
Change in setuptools after latest release of setuptools 61.0
with breaking changes which are not backwork compatible,
details in related bug and [1].
Users that don't set ``packages``, ``py_modules``, or ``configuration`` are
still likely to observe the auto-discovery behavior, which may halt the
build if the project contains multiple directories and/or multiple Python
files directly under the project root.
To disable auto discovery, one can do below in setup.py
~~~
setuptools.setup(..,packages=[],..)
~~~
or
~~~
setuptools.setup(..,py_modules=[],..)
~~~
[1] https://github.com/pypa/setuptools/issues/3197
Change-Id: Ia544d7d82c0569c453f7cb75885b903d2e3cf83f
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: Ie99a9a10eb6266bf32c4dcde6f22e25fe7f9542a
The tenant argument of RequestContext is longer available since
oslo.context 4.0.0. This change removes usage of the deprecated
argument in unit tests to prepare for version bump.
Change-Id: I0493b5fbe09d183e57a207c1dda0b2ee7a4e1b34
Use retry_state parameter that contains all information about
current retry invocation in the prepare_attempt callback.
Change-Id: Ib47b6335b591850965132448befb7b3dbe31984a
Task: 44471
Python 2 support was removed during Ussuri cycle. This change adds
the classifier to clearly state that only Python 3 is supported.
Change-Id: Icaa8acc04019b67628e84b1fa252e3731d526f08
Since croniter 1.2.0, day=0 is no longer accepted as a valid value[1].
Because of this change, some unit tests are failing with the following
error.
Invalid CRON expression: [* * 0 * *] is not acceptable, out of range
This change updates the pattern used in unit tests so that the value
is accepted by the latest croniter.
[1] 17953c8fa7
Change-Id: Ib9ee765e89716583b8f28cc9aafd9cb4e8e8e1cb
In support of the OSC migration, we need
to bump the lower-constraint for the
openstacksdk to allow for feature parity.
Change-Id: Ide69f84a76f06814cf74b73b57729f23dea1062b
The messages returned are slightly different when run
with Python 3.10.
Story: 2009741
Task: 44177
Change-Id: I26917aefdf43bf3f9008891d2e66aef9b94f58b5
Unfortunately few projects like mistral/zaqar have little participation
and are kind of unmaintained atm, we should stop testing them in CI.
Recently zaqar is broken with latest pymongo (4.0).
Change-Id: I33d3aceacf03ad1baf29301885a8e88b17b7e476
This is broken after pyparsing was bumped to 3.0.6. With
python-aodhclient (kind of unmaintained it seems) CI broken,
we should skip the test temporarily until [1] is merged and
we've a client released with the change.
[1] https://review.opendev.org/c/openstack/python-aodhclient/+/819393
Change-Id: Ib4a244087038f698eabbf2180eff3efce3a3c767
OpenDev infra only keep around the latest two Fedora releases in their
mirrors. Probe for the image from the local test mirror, but if not
found, fallback to upstream. This will be much less reliable, but can
avoid gate breakage until new images can be used.
Also, use endpoint_type when creating keystoneclient
Keystone admin endpoint has been removed from devstack with[1].
This would use the public endpoint by default.
Change-Id: I96ab14871ee8c5d5b83cc0cd4abc840ef0218ca8
When sorting resource candidates in `_get_best_existing_rsrc_db`,
resources with the same score are sorted by `updated_at`, which can be
`None`. If that is the case, use `created_at` instead.
Task: 43815
Story: 2009653
Change-Id: Ic0265fcf7ceb811803cdebaa8932fe80dc59a627
If there is underlying issues in Keystone that
causes the create stack project to fail the exception
is never caught causing the stack to never enter a failed
state with any feedback. See [1] for example.
This changes so that we catch all exceptions and set the
stack to a failed state. We do not want to return the
complete exception since it can contain information about
the deployments underlying issue so we instead log the
exception.
[1] https://paste.opendev.org/show/810161/
Change-Id: If0bc726d8681fff2b45a3b353ae627c86eb298d2
When users set max_nova_api_microversion in heat.conf, we should
use that to create the client.
Change-Id: If74f3f869fc696c87540357d96b039b68c456539
Task: 43661
The six library was introduced to bridge the gap
between Python2 and 3. This is no longer necessary
on branches where we are not supporting Python2.
Change-Id: I7736373d03c23884158e4a1d41defafb4e2b8a4c
