summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* stable-only: Pin bandit to 1.7.4 to fix the gatestable/victoriaTakashi Kajinami2023-05-161-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. NOTE(elod.illes): this patch was squashed into another gate fixing patch and backported all the way back to stable/wallaby, but those are not necessary here in victoria. Gate should pass without those. So this fix is directly backported from yoga. Change-Id: Ie552e6398c10797e4df4afe757760c48ca7f80af (cherry picked from commit 6a4c7b57b8383bef4a02fb485e781c4cbb2a03d8) (cherry picked from commit 66bba4ad21d0e405dfd209e2216a3173cda58dda) (cherry picked from commit 487fadf5c754e522b3edd02d7a2ec08223399cad)
* Ignore resource_data decryption errorsramishra2023-01-231-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) (cherry picked from commit 83a983678cdfde938e42db15c17fbc775cb88cac) (cherry picked from commit b135a99575ed42882d17b4bef2006a10cfe8afaa) (cherry picked from commit 23a6768ab11ec04e698b4e0cc7ab8c094f4616e8)
* Allow deleting user_creds when can't be decryptedramishra2022-11-171-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) (cherry picked from commit c3a8e3d64ebb37ab83b3cebb868cd68d4135f59d) (cherry picked from commit c37ec5180cefbc992640bdb2e80ed67b92dc5664) (cherry picked from commit 8d609ba98c9365fb089d5a98e3980ad9f5214946)
* Merge "Remove TripleO job" into stable/victoriaZuul2022-10-061-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. (yoga to xena) Conflicts: .zuul.yaml Change-Id: I1b99f8d039271bff8e64d64ad5482231bf2a2118 (cherry picked from commit b3430d9fc2d82820ea14d21381efabe5e22f8925) (cherry picked from commit c2b8f3c710b05b24c075a98204de9e121a0dc743) (cherry picked from commit e6a8e66c78f36b9b7f609a8ec7f80e48b155b957) (cherry picked from commit 044b094e237b4bade1a84a209a94314315e4a989)
* | zuul: Declare queue at top levelTakashi Kajinami2022-09-281-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) (cherry picked from commit f4904ff7af40c8683d0dd3550eaf979fa90a2e47) (cherry picked from commit 782da94b34d17b2bf06ba8bf06f43c091c52266f) (cherry picked from commit 167ece3673f6db5db8694dff9644a73216697185)
* | Don't always replace FAILED ServerGroup resourcesRabi Mishra2022-07-152-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Conflicts: heat/tests/openstack/nova/test_server_group.py Fixed conflicts caused by 74164424016702bac6d52c6618360287ce7ea461 , which is present in stable/xena and later. Task: 45748 Change-Id: I096dff2b541a5aa8afbbbcea5161e7ca1c244039 (cherry picked from commit a0e072b3204d736b9a4a5b2ceb2157f57405ac6f) (cherry picked from commit f9f5d2cc368e5f850b962c8d89669a50544058d1) (cherry picked from commit ead7cd61bd685ea46dd21c4ef3ea6b3fde273c10) (cherry picked from commit a4f2f6053c8b45b1e9182caad4a8af44e29ae96d)
* | Use openstack commands in upgrade pluginRabi Mishra2022-07-151-3/+3
| | | | | | | | | | | | | | | | Change-Id: I94075f261ce095c509635aab395df42878aceb1c (cherry picked from commit e446ecbb21c2c6e8909ec20121536073d66bbcb7) (cherry picked from commit 08a0a218ef406d3027fd28be8e77f9876fd10f4d) (cherry picked from commit 65fb6c7dadee7412213eeea1b36bf9befcfd5873) (cherry picked from commit da071a07d509b8f589f934db1aaeee6daff40bd3)
* | Merge "Fix timeout calc of nested resource groups" into stable/victoriaZuul2022-07-062-15/+13
|\ \
| * | Fix timeout calc of nested resource groupsBalazs Gibizer2022-01-142-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 (cherry picked from commit ef731bca05ea683c30448a2db397ae631c121d95) (cherry picked from commit f3c74a6632c5ced8c25f5811315e3d943be13c17) (cherry picked from commit 6002015fec472e0c90c91055f1963f323a1793e7)
* | | Merge "Reproduce bug story/2009237" into stable/victoriaZuul2022-07-061-0/+62
|\ \ \ | |/ /
| * | Reproduce bug story/2009237Balazs Gibizer2022-01-141-0/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) (cherry picked from commit 74280022e8dbe306c59a49f73b78ab40688fe6a6) (cherry picked from commit a5e713b62235fd91e7edc89cc951b30dcb2e7c86)
* | | Merge "Adopt grenade to multinode setting" into stable/victoriaZuul2022-07-061-2/+29
|\ \ \ | |/ /
| * | Adopt grenade to multinode settingricolin2022-01-141-2/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Change parent for grenade-heat-multinode job to grenade-multinode * Use HOST_TOPOLOGY to specify multinode. * Add irrelevant-files Change-Id: I2abdf09bcd65441006f5315321e016e02704d6f1 (cherry picked from commit ba7d105c8b866f8f30e7b0084808b813d28ef638)
* | | Merge "Remove grenade-heat and heat-functional-non-apache" into stable/victoriaZuul2022-07-061-9/+2
|\ \ \ | |/ /
| * | Remove grenade-heat and heat-functional-non-apachericolin2022-01-141-9/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch propose to remove following two jobs: * grenade-heat: Since we also run grenade-heat-multinode job, I can't think of any reason to run both `all in one` version and `multinode` version. * heat-functional-non-apache Change-Id: I081d2656eb2f20501b20e267afd19b91c73bd39a (cherry picked from commit 253aff806bf95bd8426cadc104c4fe068bcd7ea7)
* | | Make grenade job voting againTakashi Kajinami2022-07-052-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because change I7d1017bcd7147329c4e187336daee1a1ae280fa9 was backported to the previous stable branch. Backport note: This includes the following follow-up commit. (commit fee8c40c23fb160a4fe64e95a71f827528287690) Use constraints when creating venv for grenade As a followup for change I6a8cffdc86c895eebe4269c5cd37841325566c54 let's use branch specific upper constraints when running tests in grenade. Change-Id: I2de594258231e3f1c217904afce88a83a8f94df3 (cherry picked from commit fee8c40c23fb160a4fe64e95a71f827528287690) (cherry picked from commit 03e4f9af62ed66a4df72f5da793f8ce4caf8ac3e) (cherry picked from commit e3ec8946b3de50c76b2c3b08c2f7356842d3f45a) (cherry picked from commit b4d159b87e606024d65bb285576c64bd1c72fecd)
* | | Drop lower-constraints.txt and its testingGhanshyam Mann2022-06-164-170/+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 lower-constraints.txt Change-Id: I703229320320295b4a90e72c543f8959f85daaa9 (cherry picked from commit 49cbb92ed611899728425877e86396a70f5d7c5f) (cherry picked from commit 80ce36214bf2d8b2e28740916b2e87ee9e10ae44) (cherry picked from commit d1c0f628945caca01b0c986adf97e93e7795cf49) (cherry picked from commit 5a6bff198752e5e984c080bcdce5b690dabb63db)
* | | Use constraints when creating tempest venvramishra2022-06-157-10/+33
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. Backport note: Change I7d1017bcd7147329c4e187336daee1a1ae280fa9, which replaced f33 by f66, is merged into this backport to unblock CI. Change-Id: I6a8cffdc86c895eebe4269c5cd37841325566c54 (cherry picked from commit 22c48f57bb29ed62a8c3249ab953043cfd2617d3) (cherry picked from commit b95e6025f61417e7abc24a26d991bd26c57ee444) (cherry picked from commit 92db02a56e85dd5f890160217a16dc99394b927d) (cherry picked from commit d05b683ef65996ae5d1d6cc31d547169669abf45)
* | Fix None comparision when sorting by `updated_at`Erik Panter2022-04-132-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 (cherry picked from commit 403fa55fe94ae1063d2cb4b8db3b63b76b1ee5cf) (cherry picked from commit 5ea5276a3e76829fd72345e3aae7482cbd260b51) (cherry picked from commit aa31864de4fe480674a0669c05a024ab28c3c429)
* | Use neutron client for server.addressesHarald Jensås2022-02-242-72/+131
|/ | | | | | | | | | | | | | | | The server.addresses (/servers/{server_id}/ips) endpoint can contain stale data causing attribute lookups to fail. This change replaces the use of server.addresses and instead uses the neutron client to list ports with 'device_id' matching the server id. Story: 2008632 Task: 41843 Related: RHBZ#1902230 Change-Id: I1b9293041f2ad92eac0e9bc9646e7b2d7c6f7fd0 (cherry picked from commit 45750c603ac9965afd5b4e53ecff65977b887b95)
* Provide install_command to pip install with upper-constraintsvictoria-em15.1.0Brendan Shephard2021-11-201-0/+1
| | | | | | | SQLAlchemy latest (1.4.27) installed with docs job breaks it. Change-Id: Ida63e1d865dc0b2ac6a13594455962f53068c931 (cherry picked from commit 7f15b14d800654474ccab26af40384ab4515a657)
* Fallback to upstream for Fedora imageIan Wienand2021-11-041-1/+10
| | | | | | | | | | | 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/+/816603 Cherry-Picked-From: f7574531d3dc3bbbf55fd7c17d55a10b5320c5ff Change-Id: I96ab14871ee8c5d5b83cc0cd4abc840ef0218ca8
* Revert "Make grenade job voting again"Rico Lin2021-10-181-2/+2
| | | | | | | | | This reverts commit 7ef31c2beb8c40c3ddaae19167923076d2907275 and makes the grenade jobs voting. Reason for revert: The `grenade-heat-multinode` is already defined in same yaml file. We should remove grenade-heat instead, as we already have `grenade-heat-multinode` Change-Id: I9da08239fb9499b26483ebba141d1a01d94c92c3
* Make grenade job voting againBrendan Shephard2021-10-121-3/+2
| | | | | Change-Id: Ia65dabd7e357ad4ed8076fef3a3134c87100d4ed (cherry picked from commit 42b5f68bf047252a7ec6e0db98f0546c042286f3)
* Don't create deployment when changing transportramishra2021-10-101-22/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Earlier when changing software config transport we used to create a dummy deployment to push the metadata. However this would not work with convergence as we take resource lock for the update which updates the config transport (another engine would try to update the resource metadata for deployment when one engine has locked it). Currently it works when updating transport as we ignore the error in creating dummy deployment, but if there are any new depoyments for the server they would fail. We don't need to push the metadata as it would be pushed when the there is a new/updated deployment. Few additional changes in the patch: - We don't need to ignore the error as servers are now not replaced if the resource is in ERROR when nova server is good/ACTIVE. - Delete the existing tempurls and zaqar queues when changing transport. Task: 41744 Change-Id: Id592b29df36320d8697bd370252ada02612ba7d0 (cherry picked from commit 79fb6509a9c6ac5438d00d1eb858a4f5b014e6e3)
* Update get_hosts to use available APIDavid J Peacock2021-09-102-30/+22
| | | | | | | | | | | os-hosts was deprecated in nova quite some time ago. This patch updates get_hosts to use the available os-hypervisors functions. Change-Id: I36421e9859a266f0278c1b5f2acb4ebbacbfca82 Story: 2006584 Task: 36708 bz: 1740567 (cherry picked from commit aab68ced6a84c9fa39adb2cb9bb19165e699ff3a)
* Merge "Detect EL8 platform-python" into stable/victoriaZuul2021-09-011-0/+9
|\
| * Detect EL8 platform-pythonLuke Short2021-08-181-0/+9
| | | | | | | | | | | | | | | | Otherwise, this script fails to run on Enterprise Linux 8 distros. Change-Id: I0168b380d0e201d9c8f8121b384d25a2412c2129 Signed-off-by: Luke Short <ekultails@gmail.com> (cherry picked from commit 2d692e22f42bc64476ab01ff7e8c4d4717ef3786)
* | Use Block Storage API v3 instead of API v2Takashi Kajinami2021-08-2611-53/+14
|/ | | | | | | | | | | | | | | | | | | | | | | 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/victoria. Depends-on: https://review.opendev.org/802150/ Change-Id: I6a2b5afa13480791971bbd8bba1f43b9f2db8294 (cherry picked from commit 1828df32fa946d49d8449ff1d8a26c05b3990a65) Move testing to Fedora 33 Now that the gate is unblocked, we can also test F33 for gating purposes here. Change-Id: Ie1c9075623d85b27aaf1ac67a3063e219726bc6f (cherry picked from commit 6a9c35d89804057b56e1b0b995265ce3eb68129d)
* Preserve order in list_concat_uniqueramishra2021-04-262-7/+9
| | | | | | | | | | Also, we should not modify a list when iterating over it. Task: 42359 Closes-Bug: #1925373 Change-Id: Iaa2c05b4155d93f44de60b6f98a69450c1512817 (cherry picked from commit a8f8528d1ea1952cf76bd09fd27cbd65a978af65)
* Merge "Assume interface detach called for port not found" into stable/victoriaZuul2021-04-192-2/+2
|\
| * Assume interface detach called for port not foundramishra2021-04-142-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | If the interface has been detached before we call detach_interface, then we keep on calling it as we get a 404 from nova. Let's assume it's being called and check if the interface has been detached. Task: 42195 Change-Id: I768eeb10c2c24a0c93749b11636ef3e003ecfcd9 (cherry picked from commit 6ff0dc2e19ddf3a3447810f8a55b29d9bec52136)
* | Merge "Resume testing grenade jobs in Victoria" into stable/victoriaZuul2021-04-141-2/+0
|\ \
| * | Resume testing grenade jobs in Victoriaricolin2021-04-141-2/+0
| | | | | | | | | | | | Change-Id: Ie7898f025d028f6d511b7bb21c5681b9dce7b8ec
* | | Merge "Net attr: Sort segments without name attribute first" into ↵Zuul2021-04-142-1/+22
|\ \ \ | |_|/ |/| | | | | stable/victoria
| * | Net attr: Sort segments without name attribute firstHarald Jensås2021-03-052-1/+22
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Useing get_attr, pulling index 0 in the segments list of a network to associate the a subnet with the "first" segment is useful since the "first" segment is created by neutron behind the scenes on network create. A resource reference cannot be used since the "first" segment is'nt a heat resource. The issue is the order of the segments list is'nt reliable. On stack update index 0 may be a different segment, and we end up trying to update the segment_id for a subnet. Changeing the segment association is not allowed, so the stack update fails. While not perfect, sorting the list so that segments where name is None comes first will ensure that index 0 can be used. The template author should ensure segments defined in the heat template all have a names set, so that only the segment creted implicitly by neutron have 'None' name. Closes-Bug: #1894920 Change-Id: I097aba2a97144327bec188e6c71629d0f6c95901 (cherry picked from commit 539b2a4c4993787db0cd71750d3d159e584deccb)
* | Don't update status for replaced resourceramishra2021-04-024-12/+2
|/ | | | | | | | | | | | | | | With I04e7ad90944c2d03ce0e59ba16af9d60d6e01222 we allowed update of previously-existing resource if replacement creation has failed during last update. However, we force update the status of the existing resource to 'COMPLETE'. Therefore, in the next update if properties/type has not changed for the resource it won't try to update/replace the previously existing resource resulting in false positive of stack updated successfully. Task: 42194 Change-Id: Icc90a921ec67e49aec2c4acfad72235c57c78421 (cherry picked from commit bfbaab107d709c37548a22239b952c6221b9ac85)
* Merge "Delete the default value of domain in role creation" into stable/victoriaZuul2021-01-212-2/+14
|\
| * Delete the default value of domain in role creationyanpuqing2020-11-162-2/+14
| | | | | | | | | | | | | | | | | | | | | | The default value of domain caused the user to be unable to create role which no domain. The patch delete the default value of domain. Change-Id: Ic67b22c435e29f67bafa8e14ab502ebec5b07ec5 Story: 2002671 Task: 22488 (cherry picked from commit e5b00ddfafe2613440fd4992ca468b805276e58a)
* | Merge "Add SOURCE_IP_PORT to LB_ALGORITHM allowed values" into stable/victoriaZuul2021-01-192-2/+6
|\ \
| * | Add SOURCE_IP_PORT to LB_ALGORITHM allowed valuesKevin Carter2020-11-172-2/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds SOURCE_IP_PORT to lb_algorithm property of OS::Octavia::Pool resource which is missing from the available options and required when using the OVN provider driver. [0] https://docs.openstack.org/ovn-octavia-provider/latest/admin/driver.html#limitations-of-the-ovn-provider-driver [1] https://docs.openstack.org/releasenotes/octavia/train.html Story: 2008361 Task: 41268 Change-Id: Ibed37eea817a5125c5751b2bc9f44acf3c016fe1 Signed-off-by: Kevin Carter <kecarter@redhat.com> (cherry picked from commit 20b599cdf893af5165b07b3d1f70864693ec35ff)
* | Fix args for initializing trove clientLingxian Kong2021-01-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Trove client is using the 'retries' as 'connect_retries' when instantiating trove Client. Ref: https://github.com/openstack/python-troveclient/blob/master/troveclient/client.py#L469 Story: 2008422 Task: 41366 Change-Id: I58a6e235410e2ca28b3822400151621c18ad882d (cherry picked from commit defb617ce543e3e896a4ce1ef0293f4e76c5f2c0)
* | Fix multiple gate issuesramishra2021-01-122-10/+10
| | | | | | | | | | | | | | | | - Remove B322 bandit from exclusions - Fix tests for db resource update exposed by SQLAlchemy>=1.3.21 Change-Id: I18efbbbe211a42325a946f5ca74b4e26bfb3316e (cherry picked from commit f4ab9d0bc05e92f5cfb0067435d0acbb7a284695)
* | Align lower-constraints for new pipRabi Mishra2020-12-103-7/+11
| | | | | | | | | | | | | | | | New pip version is quite strict and does not allow conflicting minimum version deps in lower-constraints. Change-Id: Ie524c54e3b982bc6b0786c875d34d177444ec6fc (cherry picked from commit 4370af157262d953ed32c857a9ddb06968f3ab58)
* | Replace Fedora test image with F32Matthias Runge2020-12-075-8/+12
| | | | | | | | | | | | | | | | | | | | | | | | Fedora 31 was retired and the image is gone from mirrors. heat-cfntools have been dropped from fedora images, disable the test till that's resolved. Also makes grenade job non-voting, till this is backported to stable/victoria. Change-Id: Id869f83a46454897c2fe7a532eebfa2863befe5e (cherry picked from commit 61e53c4eca3bc4f0c60754269cb2811afc569705)
* | As of nova microversion 2.57, personality is deprecatedDavid Hill2020-11-162-1/+50
|/ | | | | | | | | | This patch returns a stack validation error if the nova microversion is 2.57 or greater and the personality parameter is also specified in the templates. Change-Id: I0919150baa36112ccbd8bfd7ccebc7aab5735cf3 Task: 41229 (cherry picked from commit b068f45adda72fa12f50008a603c8f37fcabcdff)
* Configure swap as beforeRabi Mishra2020-11-031-0/+2
| | | | | | | | | | | https://review.opendev.org/750941 changed the default swap to 1024MB for jobs and this seems to resulting in high failure rate of the functional and grenade jobs. Let's configure it back to what used to before i.e 8192MB. Change-Id: I627f2df7f6135b3d194e7146ae45c3b7f8b6394d (cherry picked from commit f419923a0d3aa62485296ab7666485e74af57c8e)
* Update TOX_CONSTRAINTS_FILE for stable/victoriaOpenStack Release Bot2020-09-221-2/+2
| | | | | | | | | | | | 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/victoria branch, tests will continue to use the upper-constraints list on master. Change-Id: Ie987f60222c1690fe3b180385f8ee891adea0fb1
* Update .gitreview for stable/victoriaOpenStack Release Bot2020-09-221-0/+1
| | | | Change-Id: I69ef54b773e870f0ecc345278835c88b6ccd824d
View Lorry Controller Status