summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Added a unit test for get_environment_hidden_param18.0.1stable/yogaChengen Du2023-03-291-0/+50
| | | | | | | | | | | 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)
* Honor 'hidden' parameter in 'stack environment show' commandChengen Du2023-03-293-2/+19
| | | | | | | | | | | | | 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)
* Merge "Decode UTF-8 body data in SwiftSignal" into stable/yogaZuul2023-03-152-54/+59
|\
| * Decode UTF-8 body data in SwiftSignalZane Bitter2023-02-062-54/+59
| | | | | | | | | | | | | | | | Change-Id: Ie12c2df93f846629a7c8b7c6415cebc31eaba1bc Story: #2010485 Task: 47053 (cherry picked from commit a0ff4b98b700c7f31a9f14d3d62eeaf3b2047139) (cherry picked from commit 6343b64e703221402f0d40fc0e62da944551e2dd)
* | stable-only: Pin bandit to 1.7.4Takashi Kajinami2023-03-151-1/+1
|/ | | | | | | | | | 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)
* Fix setting the tempest virtual env constraints env varGhanshyam Mann2023-01-283-3/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Ignore resource_data decryption errorsramishra2023-01-191-3/+8
| | | | | | | | | | 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)
* Allow deleting user_creds when can't be decryptedramishra2022-11-151-2/+4
| | | | | | | | | | 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: Declare queue at top levelTakashi Kajinami2022-09-271-1/+1
| | | | | | | | | | | | | | 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)
* Merge "Don't always replace FAILED ServerGroup resources" into stable/yogaZuul2022-07-142-5/+47
|\
| * Don't always replace FAILED ServerGroup resourcesRabi Mishra2022-07-132-5/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | Followup to I7736373d03c23884158e4a1d41defafb4e2b8a4cPavlo Shchelokovskyy2022-07-141-1/+1
|/ | | | | | | | | | | 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)
* Use openstack commands in upgrade pluginRabi Mishra2022-07-131-3/+3
| | | | | Change-Id: I94075f261ce095c509635aab395df42878aceb1c (cherry picked from commit e446ecbb21c2c6e8909ec20121536073d66bbcb7)
* Fix parameter merging with merge strategiesRabi Mishra2022-07-042-15/+16
| | | | | | | | | | | | | | | | | | 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)
* Use constraints when creating venv for grenadeRabi Mishra2022-07-012-2/+6
| | | | | | | | | 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)
* Fix AttributeError in Python 3.8Takashi Kajinami2022-06-212-6/+51
| | | | | | | | | | | | | | | | | | | | | | 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)
* Merge "Remove TripleO job" into stable/yogaZuul2022-06-211-3/+0
|\
| * Remove TripleO jobTakashi Kajinami2022-05-251-3/+0
| | | | | | | | | | | | | | | | | | | | 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)
* | Merge "Drop lower-constraints.txt and its testing" into stable/yogaZuul2022-06-164-169/+4
|\ \
| * | Drop lower-constraints.txt and its testingGhanshyam Mann2022-06-164-169/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | | Make grenade job voting againTakashi Kajinami2022-06-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | Because change I7d1017bcd7147329c4e187336daee1a1ae280fa9 was backported to the previous stable branch. Change-Id: I2de594258231e3f1c217904afce88a83a8f94df3 (cherry picked from commit fee8c40c23fb160a4fe64e95a71f827528287690)
* | | Merge "Use constraints when creating tempest venv" into stable/yogaZuul2022-06-152-2/+24
|\ \ \
| * | | Use constraints when creating tempest venvramishra2022-06-142-2/+24
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* | | Log parameters mergedrabi2022-06-141-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | This can help in troubleshooting. Task: 45579 Change-Id: I6aee0719b0cdef2b17666a43074c5c18645fc180 (cherry picked from commit c0be1f01fd9c208130857efd7c01ece94d4fb0bb)
* | | Use previous parameter merge strategyrabi2022-06-142-3/+19
|/ / | | | | | | | | | | | | | | | | | | | | | | 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)
* | Use f36 instead of f33 for testingMatthias Runge2022-05-315-8/+9
|/ | | | | | | F33 is unsupported for a while. We should not use it for any testing. Change-Id: I7d1017bcd7147329c4e187336daee1a1ae280fa9 (cherry picked from commit 78244c5f0f26064cd53b68e13fa8c4f0e235e698)
* Update TOX_CONSTRAINTS_FILE for stable/yogaOpenStack Release Bot2022-03-081-4/+4
| | | | | | | | | | | | 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
* Update .gitreview for stable/yogaOpenStack Release Bot2022-03-081-0/+1
| | | | Change-Id: I01889f3e6c1c36b4fbbae8a9ae8f9193649fa126
* Fix compatibility with oslo.context >= 4.0.018.0.0.0rc118.0.0Takashi Kajinami2022-03-018-38/+38
| | | | | | | | 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
* Fix for tenacity 8.0.1rabi2022-02-111-2/+2
| | | | | | | | Use retry_state parameter that contains all information about current retry invocation in the prepare_attempt callback. Change-Id: Ib47b6335b591850965132448befb7b3dbe31984a Task: 44471
* Add Python 3 only classifierTakashi Kajinami2022-02-081-0/+1
| | | | | | | 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
* Fix unit tests for croniter>=1.2.0Takashi Kajinami2022-01-171-2/+2
| | | | | | | | | | | | | | | 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
* Bump lower constraints for OSCbshephar2022-01-122-2/+2
| | | | | | | | In support of the OSC migration, we need to bump the lower-constraint for the openstacksdk to allow for feature parity. Change-Id: Ide69f84a76f06814cf74b73b57729f23dea1062b
* Merge "Fix Pool resource update for session_persistence"Zuul2021-12-242-2/+9
|\
| * Fix Pool resource update for session_persistencerabi2021-11-172-2/+9
| | | | | | | | | | | | | | | | Pool session_persistence property should be update allowed. Task: 43952 Change-Id: Idee8893844bfd776a81c9e3ac45aa6804092a440
* | Merge "Updating python testing classifier as per Yoga testing runtime"Zuul2021-12-242-1/+2
|\ \
| * | Updating python testing classifier as per Yoga testing runtimeGhanshyam Mann2021-12-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Adjust self.assertRaisesRegex messages for py310Corey Bryant2021-12-132-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | The messages returned are slightly different when run with Python 3.10. Story: 2009741 Task: 44177 Change-Id: I26917aefdf43bf3f9008891d2e66aef9b94f58b5
* | | Merge "Imported Translations from Zanata"Zuul2021-12-0711-57/+13
|\ \ \
| * | | Imported Translations from ZanataOpenStack Proposal Bot2021-11-0211-57/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | For more information about this automatic import see: https://docs.openstack.org/i18n/latest/reviewing-translation-import.html Change-Id: Ie693d500eb35af94e13069d85516dc42a5f811dd
* | | | Don't test zaqar in CIrabi2021-12-031-3/+0
| |/ / |/| | | | | | | | | | | | | | | | | | | | 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
* | | Skip aodhclient plugin testrabi2021-11-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "Fix None comparision when sorting by `updated_at`"Zuul2021-11-222-6/+26
|\ \ \
| * | | Fix None comparision when sorting by `updated_at`Erik Panter2021-11-092-6/+26
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Fix broken devstack pluginrabi2021-11-191-16/+17
| |/ |/| | | | | | | | | | | This devstack plugin seems broken with devstack secure rbac changes to use OS_CLOUD. Change-Id: I9f0d3d97e4cc7d5ed6858eca9c042fedb14139d1
* | Add intersphinx_mapping for sqlalchemyrabi2021-11-171-1/+5
| | | | | | | | | | | | | | This would fix the docs build failures with sqlalchemy 1.4.27. Change-Id: Iae37cb89667ae95d93eca7ea71122b7de59cee7f
* | Fallback to upstream for Fedora imageIan Wienand2021-11-126-1/+22
|/ | | | | | | | | | | | | | 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
* Merge "Fix timeout calc of nested resource groups"Zuul2021-11-012-15/+13
|\
| * Fix timeout calc of nested resource groupsBalazs Gibizer2021-09-212-15/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge "Reproduce bug story/2009237"Zuul2021-11-011-0/+62
|\ \ | |/
View Lorry Controller Status