| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
A unit test for verifying that hidden parameters should
be masked in the get stack environment API
Story: 2010555
Task: 47229
Change-Id: I44ef26849ebb450a5643907a0ef47166cfd9b1cb
(cherry picked from commit bdcb2c3bd115f1893baeab1d946eefa4aab49552)
(cherry picked from commit 89b57e5e2eee091f18afbc03e83536109388dcb6)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport note:
This includes change I0abbd535aacc03446ada0fa806dfdfdaa4522afe which
fixed the wrong explanation in the release note file.
Related-Bug: #1999665
Story: 2010484
Task: 47052
Change-Id: Ifc51ff6a4deab05002ccded59383416f9a586aa0
(cherry picked from commit c1b5fcfbe37d3f94d5b73ae36e071d1aa8c4e0f5)
(cherry picked from commit 436ecad6511b30683f6b9af4e484ed64c3bcaab9)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Change-Id: Ie12c2df93f846629a7c8b7c6415cebc31eaba1bc
Story: #2010485
Task: 47053
(cherry picked from commit a0ff4b98b700c7f31a9f14d3d62eeaf3b2047139)
(cherry picked from commit 6343b64e703221402f0d40fc0e62da944551e2dd)
|
|/
|
|
|
|
|
|
|
|
| |
bandit 1.7.5 introduced the new lint rule with which current heat code
is not compliant. This pins bandit so that any new lint rule does not
affect pep8 job in stable branches.
Change-Id: Ie552e6398c10797e4df4afe757760c48ca7f80af
(cherry picked from commit 6a4c7b57b8383bef4a02fb485e781c4cbb2a03d8)
(cherry picked from commit 66bba4ad21d0e405dfd209e2216a3173cda58dda)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Heat upgrade script set the env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE
which are used to use the constraints during Tempest virtual env
installation. Those env var are set to non-master constraint when
we need to use non-master constraints but when we need to use the
master constraints we do not set/reset them point to master constraints.
This create the issue when this grenade script install the tempest with
stable constraints but with master Tempest and as there is mismatch of
constraints now with fasteners of stable branches. Below is failure
of heat greande job on stable/yoga
- https://zuul.opendev.org/t/openstack/build/3aaec4d59bb84068bb4d4428ea747cbd/log/controller/logs/grenade.sh_log.txt#3245
Similar way, role should set stable constraints only for the stable EM branch
not for all otherwise it fail when constraints/requirements are bumped.
- https://zuul.opendev.org/t/openstack/build/74f86b8097f44c35acaffdcfe41d9693
We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.
Closes-Bug: #2003993
Change-Id: I024cd134577338fc1075e7742df7f006dc914646
(cherry picked from commit dbbba907d396158ce3bf3a207a8875b9fbb5a5b1)
(cherry picked from commit b29266398fbb4e623faaa6a894de2a33bb2846a7)
|
|
|
|
|
|
|
|
|
|
| |
If the auth_encryption_key changes We can possibly
ignore these errors when deleting stacks.
Task: 42056
Change-Id: I326e415db194a5b9c67acd038d7d2d993293ecb3
(cherry picked from commit 9407b4897e77db24bf1948153afbb1479d5dad42)
(cherry picked from commit af617facc5d6a63f416c1a047c91a66008ee4364)
|
|
|
|
|
|
|
|
|
|
| |
There are situations when the auth_encryption_key changes
and customer wants to delete old stacks. We should allow
deleting those stacks.
Task: #42055
Change-Id: Ifc8c19e181902566d4f295fa979ab6869a4e0852
(cherry picked from commit 520e2389d3123efc9269bbf82c6c9998b6c62564)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Zuul deprecated declaring shared queues at a pipeline level with
release 4.1.0[1]. This updates the job definition to use the top level
declaration instead.
See [2] for details.
[1] https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-deprecation-notes
[2] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html
Change-Id: Ib54f5944cfd803baa4044858c097fc71f1ffb789
(cherry picked from commit 4a898171f0b512518aa94dbcdd58cfc707630af9)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ServerGroup resources work as scheduler hints for server
resources and replacement of it replaces the servers which
is undesirable in many circumstances.
- We don't allow update of ServerGroup resource properties
- If not created (CREATE_FAILED) without resource_id they will
be replaced
- If does not exist in nova they would be created
- If exist in nova, FAILED resource status would be just
changed to COMPLETE
Task: 45748
Change-Id: I096dff2b541a5aa8afbbbcea5161e7ca1c244039
(cherry picked from commit a0e072b3204d736b9a4a5b2ceb2157f57405ac6f)
|
|/
|
|
|
|
|
|
|
|
|
| |
that patch erroneously replaced dict.values() with dict.items(),
and now ExtraRouteSet can not be created due to AttributeError
('tuple' has no attribute 'has_interface').
Story: 2010142
Task: 45778
Change-Id: I2643b319f3a91f98097b96639f7298b25724aa62
(cherry picked from commit 65a68d97d0b0a4a78c2d21f6b76c6f207c993a19)
|
|
|
|
|
| |
Change-Id: I94075f261ce095c509635aab395df42878aceb1c
(cherry picked from commit e446ecbb21c2c6e8909ec20121536073d66bbcb7)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Earlier users had to specify merge strategy for
a parameter/parameter_default in every environment
file where they are used(or the defaults for that
environment was used). However, the strategy
for a parameter in the first environment was
ignored as there is nothing to merge.
With Iec3367667248d0b46196a6d569f3cbb3b200d842, we
changed to use existing merge strategies, but the
strategies in the first environment were still
ignored. This patch fixes it.
Task: 45578
Change-Id: Ic6125c6af60c1007243523cc8510a17f49c7b5af
(cherry picked from commit d9fe7301b3af2db9fa56d59eb405add94730ba50)
|
|
|
|
|
|
|
|
|
| |
As a followup for change I6a8cffdc86c895eebe4269c5cd37841325566c54
let's use branch specific upper constraints when running tests in
grenade.
Change-Id: I71f8398b6aa57b7c1910750b8e048825383e3d9a
(cherry picked from commit 39d653fa5741e45d26388950270e7ed3ca489b89)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The importlib-metadata package was imported to the core Python since
Python 3.8, and stevedore uses the standard library implementation
instead of the 3rd party package in Python 3.8 and later. However
the implementation available in Python 3.8 is quite old and especially
it does not include the change which added the module attribute[1].
This change makes sure we avoid referring to that attribute if it does
not exist, to avoid AttributeError in Python 3.8.
[1] https://github.com/python/importlib_metadata/commit/dfc96137ac3583477c02aa97291b0896fb61f282
Backport note:
This change includes an additional fix for Python < 3.8, which uses
the 3rd party importlib-metadata.
Story: 2010095
Task: 45650
Change-Id: Ieba5f353b0fe8a9b187bac1f6ff1b3a8f3b896b3
(cherry picked from commit eec1f92bc02e8beb4ce1db9646f8b3b678fb8329)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
(cherry picked from commit b3430d9fc2d82820ea14d21381efabe5e22f8925)
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As discussed in TC PTG[1] and TC resolution[2], we are
dropping the lower-constraints.txt file and its testing.
We will keep lower bounds in the requirements.txt file but
with a note that these are not tested lower bounds and we
try our best to keep them updated.
[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal
Conflicts:
.zuul.yaml
Change-Id: I703229320320295b4a90e72c543f8959f85daaa9
(cherry picked from commit 49cbb92ed611899728425877e86396a70f5d7c5f)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because change I7d1017bcd7147329c4e187336daee1a1ae280fa9 was backported
to the previous stable branch.
Change-Id: I2de594258231e3f1c217904afce88a83a8f94df3
(cherry picked from commit fee8c40c23fb160a4fe64e95a71f827528287690)
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When running tempest we run in-tree tests as well. Lots of these
tests including tempest tests may not work with new client
libraries. Let's use the relevant branch upper constraints when
running functional tests.
Change-Id: I6a8cffdc86c895eebe4269c5cd37841325566c54
(cherry picked from commit 22c48f57bb29ed62a8c3249ab953043cfd2617d3)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This can help in troubleshooting.
Task: 45579
Change-Id: I6aee0719b0cdef2b17666a43074c5c18645fc180
(cherry picked from commit c0be1f01fd9c208130857efd7c01ece94d4fb0bb)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We don't allow different parameter merge strategies
in different environment files for a parameter. If
a merge strategy has already been provided in one
environment file, let's use that for subsequent ones
unless a different merge strategy has been provided.
Task: 45578
Change-Id: Iec3367667248d0b46196a6d569f3cbb3b200d842
(cherry picked from commit 94f32ee39f4d705614079bd0ac113cde67dbb7e4)
|
|/
|
|
|
|
|
| |
F33 is unsupported for a while. We should not use it for any testing.
Change-Id: I7d1017bcd7147329c4e187336daee1a1ae280fa9
(cherry picked from commit 78244c5f0f26064cd53b68e13fa8c4f0e235e698)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/yoga branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I6856dd58d8b80c5e12fa2603abb994149a6288fa
|
|
|
|
| |
Change-Id: I01889f3e6c1c36b4fbbae8a9ae8f9193649fa126
|
|
|
|
|
|
|
|
| |
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] https://github.com/kiorky/croniter/commit/17953c8fa73d09c15b1a8af6b3f27245856f3cb1
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Pool session_persistence property should be update
allowed.
Task: 43952
Change-Id: Idee8893844bfd776a81c9e3ac45aa6804092a440
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Yoga testing runtime[1] has been updated to add py39
testing as voting. Unit tests update are handled by the
job template change in openstack-zuul-job
- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286
this commit updates the classifier in setup.cfg file.
[1] https://governance.openstack.org/tc/reference/runtimes/yoga.html
Change-Id: I573f6f4f4a9257a4c9c25a9d61a9ea29267377d1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The messages returned are slightly different when run
with Python 3.10.
Story: 2009741
Task: 44177
Change-Id: I26917aefdf43bf3f9008891d2e66aef9b94f58b5
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: Ie693d500eb35af94e13069d85516dc42a5f811dd
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |/
|/|
| |
| |
| |
| |
| | |
This devstack plugin seems broken with devstack secure rbac changes
to use OS_CLOUD.
Change-Id: I9f0d3d97e4cc7d5ed6858eca9c042fedb14139d1
|
| |
| |
| |
| |
| |
| |
| | |
This would fix the docs build failures with
sqlalchemy 1.4.27.
Change-Id: Iae37cb89667ae95d93eca7ea71122b7de59cee7f
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The timeout calculation of nested resource groups are using seconds but
then it passing the value in seconds to the stack resource that is
expected it in minutes. This leads to a rapidly increasing timeout value
in each nesting levels.
This patch converts the seconds to minutes before passing it forward.
Story: 2009237
Task: 43372
Change-Id: I3f132d4889723f7b4a3a416779ac5ee7663249b8
|
|\ \
| |/ |
|