| 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)
(cherry picked from commit 41a6b91362c3cf90bd3692c88b9840d6b1a8d56b)
|
|\ \
| |/
| |
| | |
stable/xena
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
(cherry picked from commit c50d720aa36fd7553b133a5a2f4fefdb3040211f)
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
Note:
This backport includes change Ie552e6398c10797e4df4afe757760c48ca7f80af
to unblock gate by a single commit. Also, grenade job is set non-voting
now until we identify the additional changes to fix the job.
Closes-Bug: #2003993
Change-Id: I024cd134577338fc1075e7742df7f006dc914646
(cherry picked from commit dbbba907d396158ce3bf3a207a8875b9fbb5a5b1)
(cherry picked from commit b29266398fbb4e623faaa6a894de2a33bb2846a7)
(cherry picked from commit 391684581b60bf1ca7a88f2c52898cd22cfd48f1)
|
|/
|
|
|
|
|
|
|
|
|
| |
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)
(cherry picked from commit 83a983678cdfde938e42db15c17fbc775cb88cac)
|
|
|
|
|
|
|
|
|
|
|
| |
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)
(cherry picked from commit c3a8e3d64ebb37ab83b3cebb868cd68d4135f59d)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
(cherry picked from commit f4904ff7af40c8683d0dd3550eaf979fa90a2e47)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
(cherry picked from commit ecca0fcbeb96608e56005ec40fe586f498b62f66)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
(cherry picked from commit f9f5d2cc368e5f850b962c8d89669a50544058d1)
|
| |
| |
| |
| |
| |
| | |
Change-Id: I94075f261ce095c509635aab395df42878aceb1c
(cherry picked from commit e446ecbb21c2c6e8909ec20121536073d66bbcb7)
(cherry picked from commit 08a0a218ef406d3027fd28be8e77f9876fd10f4d)
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
(yoga to xena)
Conflicts:
.zuul.yaml
Change-Id: I1b99f8d039271bff8e64d64ad5482231bf2a2118
(cherry picked from commit b3430d9fc2d82820ea14d21381efabe5e22f8925)
(cherry picked from commit c2b8f3c710b05b24c075a98204de9e121a0dc743)
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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)
(cherry picked from commit 976bcf9ef34014cdd5cf15f97243609c96ac8ee8)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
(cherry picked from commit 154691d21d24351edbe066fd23c731afad456b85)
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because change I7d1017bcd7147329c4e187336daee1a1ae280fa9 was backported
to the previous stable branch.
Change-Id: I2de594258231e3f1c217904afce88a83a8f94df3
(cherry picked from commit fee8c40c23fb160a4fe64e95a71f827528287690)
(cherry picked from commit 03e4f9af62ed66a4df72f5da793f8ce4caf8ac3e)
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
lower-constraints.txt
Change-Id: I703229320320295b4a90e72c543f8959f85daaa9
(cherry picked from commit 49cbb92ed611899728425877e86396a70f5d7c5f)
(cherry picked from commit 80ce36214bf2d8b2e28740916b2e87ee9e10ae44)
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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)
(cherry picked from commit b95e6025f61417e7abc24a26d991bd26c57ee444)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This can help in troubleshooting.
Task: 45579
Change-Id: I6aee0719b0cdef2b17666a43074c5c18645fc180
(cherry picked from commit c0be1f01fd9c208130857efd7c01ece94d4fb0bb)
(cherry picked from commit d997d70ca13065d1caf96c06af05d084353ca827)
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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)
(cherry picked from commit f0507980586711014e28411d53faba30138c3044)
|
|/
|
|
|
|
|
|
| |
F33 is unsupported for a while. We should not use it for any testing.
Change-Id: I7d1017bcd7147329c4e187336daee1a1ae280fa9
(cherry picked from commit 78244c5f0f26064cd53b68e13fa8c4f0e235e698)
(cherry picked from commit eefb921612b6d560e9f28767ba3a40e25bdd4f7d)
|
|
|
|
|
|
|
|
|
|
|
| |
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
(cherry picked from commit 403fa55fe94ae1063d2cb4b8db3b63b76b1ee5cf)
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
(cherry picked from commit ef731bca05ea683c30448a2db397ae631c121d95)
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a functional test that reproduces the bug that nested resource group
timeout value is increasing rapidly with every nesting level.
Story: 2009237
Task: 43373
Change-Id: I8e85434a5fb9cc6d0ef3240c8ae6085f5124174b
(cherry picked from commit 863d645d7ef223a2534423e623fbc1c420c8557f)
|
| |
| |
| |
| |
| |
| | |
SQLAlchemy latest (1.4.27) installed with docs job breaks it.
Change-Id: Ida63e1d865dc0b2ac6a13594455962f53068c931
|
|/
|
|
|
|
|
|
|
|
|
| |
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.
Depends-On: https://review.opendev.org/c/openstack/heat/+/816602
Cherry-Picked-From: f7574531d3dc3bbbf55fd7c17d55a10b5320c5ff
Change-Id: I96ab14871ee8c5d5b83cc0cd4abc840ef0218ca8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nova api has a different signature from microversion
2.64 onwards[1].
Also adds support_status for 'rules' property missed
earlier in I8e77f54303298da00cbe719afccb449f10fe387c.
[1] https://github.com/openstack/python-novaclient/blob/master/novaclient/v2/server_groups.py#L103-L104
Task: 43168
Task: 43661
Change-Id: If7138c71044adadaf7de255a2fac463b57ff3c47
(cherry picked from commit 9aedaa6d8ab2a799f140fd7c01ad30342d0cc2aa,
e70ff2e1533412727f8aeb3e08ffd9a8cefef6f9)
|
|
|
|
|
|
|
|
|
| |
... because it was already removed from cinder[1].
[1] e05b261af7dcd24096b229860df65dff1d385910
Change-Id: I8baf1701483ce2addd47dd4cb472f92ad4a192cd
(cherry picked from commit 271156446fe4392f116f2837aea9449e18c73579)
|
|
|
|
|
|
|
|
|
|
|
|
| |
The shared_services_types parameter defines the shared services located
in the other region. This parameter by default include volume and
volumev2 but doesn't include volumev3 which represents Bloack Storage
API v3.
This change adds volumev3 to the default items so that all of volume
services are included by default.
Change-Id: Idde186b2d88321e7902e4330780aabc369754b14
(cherry picked from commit 77bde0120b57b5c1b511279e5f4131f189ada5f8)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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/xena branch, tests will
continue to use the upper-constraints list on master.
Change-Id: Idf8ba67b0bd6155ed60474723b63e290da22a237
|
|
|
|
| |
Change-Id: I11723ab3b683c6a877433bc8ebfa9ef6b1e8a178
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add "rule" property for anti-affinity in order to set rules for
max_server_per_host on a ServerGroup as this was implemented in
nova microversion 2.64. In this patch, we allow an operator
to set add a rule on an anti-affinity policy if the nova micro
version is 2.64 or greater.
Change-Id: I8e77f54303298da00cbe719afccb449f10fe387c
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change ensures options of the oslo.cache library are included in
heat.conf generated by oslo-config-generator.
Change-Id: I89efa955e9321e246c9d339a6e5a18d44282eca6
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some circumstances, it is necessary to have
arbitrary image properties on Glance images.
An example is described here:
https://storyboard.openstack.org/#!/story/2008951
This patch adds the ability to specify those
properties using the WebImage resource.
Story: 2008951
Task: 42575
Change-Id: I23475185671c52b02eb57f1aa537f206b51c384a
|
| | |
| | |
| | |
| | | |
Change-Id: Ia65dabd7e357ad4ed8076fef3a3134c87100d4ed
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Block Storage API v2 was deprecated during Pike cycle and is being
removed during Xena cycle, and current v3 API should be used instead.
Unused volume_client and network_client in integration test code are
also removed by this change.
Note:
granade tests is made non-voting temporally until the same issue is
fixed in stable/wallaby.
Depends-on: https://review.opendev.org/802150/
Change-Id: I6a2b5afa13480791971bbd8bba1f43b9f2db8294
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise, this script fails to run on Enterprise Linux 8 distros.
Change-Id: I0168b380d0e201d9c8f8121b384d25a2412c2129
Signed-off-by: Luke Short <ekultails@gmail.com>
|
|\ \ \ |
|