summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Allow deleting user_creds when can't be decryptedussuri-eolramishra2022-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) (cherry picked from commit 15667ccb3da902f1a653b14c81719446436214a6)
* Merge "Remove TripleO job" into stable/ussuriZuul2022-10-111-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) (cherry picked from commit 40a56d353a43e167d33bb56645ad7727ea1cabfe)
* | 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) (cherry picked from commit 94cac44798a32fcdf027ee1905c69328890c5049)
* | Don't always replace FAILED ServerGroup resourcesRabi Mishra2022-07-192-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) (cherry picked from commit 007ff4447b28837e7ab6045b3a78a15bf9c1d25e)
* | Use openstack commands in upgrade pluginRabi Mishra2022-07-191-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) (cherry picked from commit 4c26fb577f0e7a0d50bbea4f274d69253032e331)
* | Make grenade job voting againTakashi Kajinami2022-07-062-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) (cherry picked from commit d7582f0032e753fdee9f5b12f17d66fd89aa4e85)
* | Merge "Fix None comparision when sorting by `updated_at`" into stable/ussuriZuul2022-06-202-6/+27
|\ \
| * | Fix None comparision when sorting by `updated_at`Erik Panter2022-04-132-6/+27
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. (victoria to ussuri) Conflicts: heat/tests/test_convg_stack.py Resolved conflict caused by the following commit. commit fd6cf83554db68752278d37f577ba984d9f831b2 Use unittest.mock instead of third party mock Task: 43815 Story: 2009653 Change-Id: Ic0265fcf7ceb811803cdebaa8932fe80dc59a627 (cherry picked from commit 403fa55fe94ae1063d2cb4b8db3b63b76b1ee5cf) (cherry picked from commit 5ea5276a3e76829fd72345e3aae7482cbd260b51) (cherry picked from commit aa31864de4fe480674a0669c05a024ab28c3c429) (cherry picked from commit 26a20de88c0b578422e9847c1210d10f10b04854)
* | Use constraints when creating tempest venvramishra2022-06-1711-179/+38
|/ | | | | | | | | | | | | | | | | | | | | | | | | | 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. Backport notes to ussuri: - Change I703229320320295b4a90e72c543f8959f85daaa9, which removed l-c job is merged into this backport because the job is failing now. - Change Ibe60d1e536f0e887eceea32b7cb4eec6318e96af is partially pulled into this change to fix the requirements-check job. - This change was adjusted to avoid config error in zuul. The grenade job is already made non-voting in stable/ussuri. Change-Id: I6a8cffdc86c895eebe4269c5cd37841325566c54 (cherry picked from commit 22c48f57bb29ed62a8c3249ab953043cfd2617d3) (cherry picked from commit b95e6025f61417e7abc24a26d991bd26c57ee444) (cherry picked from commit 92db02a56e85dd5f890160217a16dc99394b927d) (cherry picked from commit d05b683ef65996ae5d1d6cc31d547169669abf45) (cherry picked from commit 87b40ed75ea4d8f91db3d7dbec236adeb9516020)
* Use neutron client for server.addressesHarald Jensås2022-01-252-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-constraintsBrendan 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. Cherry-Picked-From: f7574531d3dc3bbbf55fd7c17d55a10b5320c5ff Change-Id: I96ab14871ee8c5d5b83cc0cd4abc840ef0218ca8
* 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)
* Merge "Detect EL8 platform-python" into stable/ussuriZuul2021-10-081-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 v2stable/ussuriTakashi Kajinami2021-08-2511-54/+17
|/ | | | | | | | | | | | | | | | | | | | | | | | | 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. Also, changes to use fedora 33 for tests. 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_uniqueussuri-em14.2.0ramishra2021-04-272-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 "Net attr: Sort segments without name attribute first" into stable/ussuriZuul2021-04-142-1/+22
|\
| * 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-044-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)
* Add SOURCE_IP_PORT to LB_ALGORITHM allowed valuesKevin Carter2021-01-202-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) (cherry picked from commit 3cf3a68a40d6a12e6abc5f2dd582b7e66a66dabc)
* Replace Fedora test image with F32Matthias Runge2021-01-148-13/+14
| | | | | | | | | | | | | | | | | | | 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. NOTE(elod.illes): the following changes were made compared to the original patch: grenade jobs don't need to be non-voting anymore. bandit removed B322 test, so it needs to be removed from tox.ini, too. Fix contradicting lower constraints to make lower-constraints job pass. Change-Id: Id869f83a46454897c2fe7a532eebfa2863befe5e (cherry picked from commit 61e53c4eca3bc4f0c60754269cb2811afc569705) (cherry picked from commit 779b39c975c32e8fd0a3982197787c294cf92589)
* As of nova microversion 2.57, personality is deprecatedDavid Hill2020-11-172-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) (cherry picked from commit 3f98fd9b1dfadf0390cc8bef9f42d08840b34840)
* Merge "Lazily cache parsed value of list/json parameters" into stable/ussuriZuul2020-10-132-22/+21
|\
| * Lazily cache parsed value of list/json parametersZane Bitter2020-09-082-22/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Parsing the value of JSON parameters at the time we create them (or update the default value) results in exceptions occurring while creating the Stack object, that are then not caught and transformed. The result is an HTTP 500 Internal Error reported by the API, with an unhelpful error message. By not parsing the JSON until it is needed, we ensure that any errors will occur during validation, where errors are appropriately transformed (to StackValidationFailed) and annotated with the necessary information to help the user determine the source. Change-Id: I70e341c344d6254173ad4519276626230087263a Story: 2007957 Task: 40443 (cherry picked from commit b603470a1207fcbc9ee30f3a3b4b457a9f83a03a)
* | Merge "Fix OS::Heat::Delay resource type" into stable/ussuriZuul2020-10-122-3/+7
|\ \
| * | Fix OS::Heat::Delay resource typeZane Bitter2020-10-062-3/+7
| |/ | | | | | | | | | | | | | | | | | | Don't override ResourceStatus.ACTIONS, as it's used internally by the Resource class. Change-Id: Icf306e981c19e3d5410905befa7907dcdba33337 Story: 2008013 Task: 40663 (cherry picked from commit c362c57854f7d841a72dd9de2f6ec3a9b9187f82)
* | Merge "Configure swap as before" into stable/ussuriZuul2020-10-121-0/+2
|\ \
| * | Configure swap as beforeRabi Mishra2020-10-091-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)
* | | Supports 'virtio-forwarder' vnic type for portEmilien Macchi2020-10-072-1/+7
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Supports the 'virtio-forwarder' vnic type for port sync with Neutron. The 'virtio-forwarder' is an indirect mode for SR-IOV interfaces used to connect the instances into the Neutron networks. It has been supported since the Queens release: I28315fb12f62dc7d52d099c211086b2b81eca39a Note that 'virtio-forwarder' is already supported by Horizon: openstack_dashboard/api/neutron.py: ('virtio-forwarder', _('Virtio Forwarder')) Nova: nova/network/model.py: VNIC_TYPE_VIRTIO_FORWARDER = 'virtio-forwarder' openstackclient: openstackclient/network/v2/port.py: choices=(...), virtio-forwarder neutron-lib: neutron_lib/api/definitions/portbindings.py VNIC_VIRTIO_FORWARDER = 'virtio-forwarder' Task: 40435 Change-Id: Ie65f8858d6d1a1854702eb33c40ea827505bfe51 (cherry picked from commit 03ab18d4599183d13dceb6d1130358f717197136)
* | Use Fedora 31 for testsRabi Mishra2020-10-075-7/+7
|/ | | | | | | | | Fedora 30 does not seem to be available anymore. http://mirror.bhs1.ovh.opendev.org/fedora/releases/ Change-Id: Ia45e957bb24f5596a5ef16271f71ba8b77df9e42 (cherry picked from commit f18a6767927965b930579995eb0b3d13c647bc26)
* Add U release codename for docs generation14.1.0Zane Bitter2020-08-121-1/+2
| | | | | | This makes for nicer output in the resource types docs. Change-Id: I5c7b0e7454df0c5dd33efb03c08d15ea231bf530
* Merge "Check external resources after creation" into stable/ussuriZuul2020-07-273-1/+16
|\
| * Check external resources after creationZane Bitter2020-07-233-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The method Resource.check() is not a generator function, but it does return a generator in most cases. Simply calling the function does not cause the resource to actually be checked. Only in the case where the resource did not provide a handle_check() method would it do anything at all - and in that case it simply changes the state to CHECK_COMPLETE. Yield the generator function so that the resource will actually be checked if the resource type supports it. Change-Id: I2a78b6f6235529a95838307e3d38731d31ff5c4b Task: 37828 (cherry picked from commit 5c6038f7a272238eef8978a4b26ab4ae4efd745b)
* | Merge "Monkey patch original current_thread _active" into stable/ussuriZuul2020-07-234-0/+24
|\ \ | |/ |/|
| * Monkey patch original current_thread _activeCorey Bryant2020-05-124-0/+24
| | | | | | | | | | | | | | | | | | | | Monkey patch the original current_thread to use the up-to-date _active global variable. This solution is based on that documented at: https://github.com/eventlet/eventlet/issues/592 Change-Id: I0540923755ac3969b584eeba2e19c037a7f2c261 Story: 2007614 (cherry picked from commit 8fd17214a97322a8a0136e50ced1d65a7d9dd75e)
* | Merge "Allow scale-down of ASG as part of update" into stable/ussuriZuul2020-07-154-39/+55
|\ \
| * | Allow scale-down of ASG as part of updateRabi Mishra2020-05-294-39/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When user wants to do manual scale-up of ASG by increasing the desired_capacity and also update some member properties as part of a stack update, if it fails due to insufficient resources when resizing, trying to manually scale-down by decreasing the desired_capacity won't work, as it would always expect to update the group with the earlier size before scaling down. This patch uses the target_size when building the batches. Task: 39867 Change-Id: Id851530b424f68b5e0e967fe34431483bfffd852 (cherry picked from commit 26d8f64fc90ed9b3ad0413ed0c932fb91b51d666)
* | | Merge "Don't check stack staus for already migrated stacks" into stable/ussuriZuul2020-07-141-4/+4
|\ \ \
| * | | Don't check stack staus for already migrated stacksRabi Mishra2020-07-031-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If stacks are already migrated to convergence, there is no point in checking stack status before returning. This will allow re-run of the command inspite of migrated stacks in FAILED state. Change-Id: Ia0e34423377843adee8efc7f23d2c2df5dac8e20 Task: 40266 (cherry picked from commit 8d5d2a8fb6145caa7aac1eb90a4787706c298e47)
* | | | Merge "Check for nova exception.Conflict rather than task_state" into ↵Zuul2020-07-143-49/+25
|\ \ \ \ | |/ / / |/| | | | | | | stable/ussuri
| * | | Check for nova exception.Conflict rather than task_stateRabi Mishra2020-07-013-49/+25
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | When detaching and attaching volumes nova would raise an exception.Conflict, if attach and detach can't happen. Let's use that to retry rather than using task_state. Change-Id: I50904e4254568cd807b9ff18eef482cadb626ce5 Task: 40169 (cherry picked from commit 01c230e793043310614d5b88096476ce0eac2c78)
* | | Use never expiring alarm_url for resource attributesRabi Mishra2020-06-256-16/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't use timestamp when generating ec2 signed url for alarm url attributes of resource. This will resolve the issue for new resources even if they are cached in attributes or resource_data. However, for existing stacks containing these resources the current best option is to not cache these attributes and allow alarm resources to be able to get a new never expiring urls in the next forced update. Change-Id: If2ebc3deacb770294004ae023500367af603b59e Task: 39985 Related-Bug: #1872737 (cherry picked from commit d0e44ded0a07cfe6b3413693d79c7f1f67b27701)
* | | Don't store signal_url for ec2 signaling of deploymentsRabi Mishra2020-06-256-12/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As part of a CVE keystone has started checking[1] the timestamp of signed ec2 token with default TTL of 15 mins. We can't store the ec2 url anymore for future use for those. This moves the caching logic to BaseWaitConditionHandle class. Conflicts: heat/engine/resources/signal_responder.py heat/tests/test_signal.py [1] https://review.opendev.org/#/c/724124/ Change-Id: I6b74faed820caccd39210bd48a212b2dedca46b9 Task: 39985 Related-Bug: #1872737 (cherry picked from commit 3047ca7d36baaa59ab2960602da956d2087a2a62)
* | | Add native grenade zuul v3 jobsLuigi Toscano2020-06-254-103/+17
|/ / | | | | | | | | | | | | | | Moved from https://review.opendev.org/#/c/639774/ Task: 40166 Change-Id: Id7f9be610e99cac9cf1f097066cc8748752d92dd (cherry picked from commit 86fc1740c405e73c094012e8d341cf9d1e71e347)
* | Fix hacking min version to 3.0.1Ghanshyam Mann2020-05-201-1/+1
|/ | | | | | | | | | | | | | | | | | flake8 new release 3.8.0 added new checks and gate pep8 job start failing. hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. Though it is fixed in latest hacking but 2.0 and 3.0 has cap for flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also break the pep8 job if new check are added. To avoid similar gate break in future, we need to bump the hacking min version. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: I4586bde1bd9f33dcdd803900bc648720073bdb62 (cherry picked from commit a61c4bbe29b4df6d00b74316d4b650727b15381d)
* Merge "Update TOX_CONSTRAINTS_FILE for stable/ussuri" into stable/ussuriZuul2020-05-061-2/+2
|\
| * Update TOX_CONSTRAINTS_FILE for stable/ussuriOpenStack Release Bot2020-04-271-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/ussuri branch, tests will continue to use the upper-constraints list on master. Change-Id: I6b4f94d7345e85f250882eb46d72e5a50df89665
* | Merge "Update .gitreview for stable/ussuri" into stable/ussuriZuul2020-05-061-0/+1
|\ \ | |/
View Lorry Controller Status