summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [stable-only] Cap virtualenv for py37stable/ussuriElod Illes2022-09-051-0/+4
| | | | | | | | | | | | py37 test started to fail with latest virtualenv (20.16.4) as it bundles setuptools 65.3.0, which causes installation problems under py37. (Note: with py38 the problem does not occur). This patch sets virtualenv<20.16.4 to unblock the gate as virtualenv 20.16.3 bundles setuptools 63.4.1, with which py37 gate works well. Change-Id: I29beb88dd241af72397bf0dd1fc46c98a229425c
* Merge "Move legacy grenade jobs to Zuul v3" into stable/ussuriZuul2021-03-158-393/+6
|\
| * Move legacy grenade jobs to Zuul v3Kenneth Giusti2021-03-028-393/+6
| | | | | | | | | | | | | | | | Also deletes obsolete playbook files for telemetry tests that have been removed. Change-Id: Ibbb811e988cc048e6c39a0c2336c716a1a0ddb30 (cherry picked from commit a5ae9f4aa0e18787b4bb676b3e725c225deae96d)
* | Correctly handle missing RabbitMQ queuesussuri-em12.1.6Hervé Beraud2021-03-024-21/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, setting the '[oslo_messaging] direct_mandatory_flag' config option to 'True' (the default) will result in a 'MessageUndeliverable' exception being raised when sending a reply if a RabbitMQ queue is missing [1]. It was the responsibility of the application to handle this exception, however, many applications are not doing so. This has resulted in a number of bug reports. Start handling this error condition, using a retry loop to attempt to resend the message and work around any temporary glitches. Since attempting to send a reply will will no longer raise an exception, there is little benefit in retaining the '[oslo_messaging] direct_mandatory_flag' config option: users setting this to False will simply not benefit from the retry logic and improved logging added here. This option is already deprecated though and will be fully removed in a future release. [1] https://www.rabbitmq.com/channels.html Change-Id: Id5cddbefbe24ef100f1cc522f44430df77d217cb Closes-Bug: #1905965 (cherry picked from commit 4937949dffecdf8863a7876e5a6b0b18e811c3ac) (cherry picked from commit 391ce7fc69adc8d713d8ca64e76d901eb3e65df1)
* | Deprecate the mandatory flagHervé Beraud2021-03-022-3/+12
| | | | | | | | | | | | | | | | It will not be possible to deactivate this functionality anymore. Change-Id: I1cbafff03349f7da9224de46285707fbf2a81a68 (cherry picked from commit 2b89d97888c9b6cd8b4f23e5ae7ce3103d5f9e5b) (cherry picked from commit 06ad070cc6dbe72d1f96c529f7bd193dbae383f5)
* | Fix some typosushen2021-03-022-5/+5
|/ | | | | Change-Id: Ic0a311d290682a923ec4f8cbe36f875d560cd41a (cherry picked from commit 2c2779a974d59a9d91bd7cb1e3ae001952fe9083)
* Fix type of direct_mandatory_flag optBen Nemec2021-02-171-6/+6
| | | | | | | | | | | | | | An IntOpt with a default of True is invalid. I'm a little surprised this doesn't fail a defaults check somewhere, but it needs to be fixed regardless. Looking at where it is used, it appears the boolean type is correct. This just changes the opt type to BoolOpt to match. Change-Id: I01a38754a31c891f2b3b9c7f8135690693df5d13 Closes-Bug: 1909036 (cherry picked from commit b8f8b17030e93f6fe64e986ebae1de4011f007d5) (cherry picked from commit a0329a3f86e8bf275dd4e16c1f354911a6ff2eb6)
* Dropping lower constraints testingHervé Beraud2021-02-173-100/+0
| | | | | | | | | | | | | | | | | | | | | | | | | We facing errors related to the new pip resolver, this topic was discussed on the ML and QA team proposed to to test lower-constraints [1]. I propose to drop this test because the complexity and recurring pain needed to maintain that now exceeds the benefits provided by this mechanismes. Also removing lower constraints and related tox environment as they are no longer needed. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html Conflicts: .zuul.yaml lower-constraints.txt NOTE(hberaud): Conflicts are due to different base jobs in zuul and different constraints in lower-constraints Change-Id: Icf48ef72fbfff88dda2714b386dbbfe355dc1acb (cherry picked from commit 686a8b61826d9bed0a989e645a13c708c3e6343c) (cherry picked from commit 1682ef69ae30732071fb4296f947047c37c4622e)
* add min of 1 to rpc_conn_pool_size12.1.5Sean Mooney2020-10-193-1/+21
| | | | | | | | | | | | | | | This change add a min value of 1 to [oslo_messaging_rabbit]/rpc_conn_pool_size such that there is always at least 1 connection avaiable. This change add a runtime check to ensure that [oslo_messaging_rabbit]/rpc_conn_pool_size is greater than or equal too [oslo_messaging_rabbit]/conn_pool_min_size Change-Id: I2ad4b9f1d012c9f0586a932ac27d96da1bcc4e4c Closes-Bug: #1899533 (cherry picked from commit 00d15eaeaba0ded0330cdcec7b19eee3adbfb1e1) (cherry picked from commit 8f5847dcbe5144272ff7295fce2b50a9f544e5b0)
* Cancel consumer if queue down12.1.4shenjiatong2020-08-213-31/+65
| | | | | | | | | | | | | | | | | | | | | | | | | Previously, we have switched to use default exchanges to avoid excessive amounts of exchange not found messages. But it does not actually solve the problem because reply_* queue is already gone and agent will not receive callbacks. after some debugging, I found under some circumstances seems rabbitmq consumer does not receive basic cancel signal when queue is already gone. This might due to rabbitmq try to restart consumer when queue is down (for example when split brain). In such cases, it might be better to fail early. by reading the code, seems like x-cancel-on-ha-failover is not dedicated to mirror queues only, https://github.com/rabbitmq/rabbitmq-server/blob/master/src/rabbit_channel.erl#L1894, https://github.com/rabbitmq/rabbitmq-server/blob/master/src/rabbit_channel.erl#L1926. By failing early, in my own test setup, I could solve a certain case of exchange not found problem. Change-Id: I2ae53340783e4044dab58035bc0992dc08145b53 Related-bug: #1789177 (cherry picked from commit 196fa877a90d7eb0f82ec9e1c194eef3f98fc0b1)
* Catch ConnectionForced Exception12.1.3shenjiatong2020-07-291-1/+3
| | | | | | | | | | Occasionally I saw large number of connectionforced exceptions. such exceptions cannot be healed automatically and requires a reboot. catch it and ensure connection established. Change-Id: I5c468d10230f05438df780e045f1e92662edf070 Closes-Bug: #1883038 (cherry picked from commit 26e8bb4cc9097fddf3c2e34599b131e3f5d73867)
* tests: Resolves issues with kombu > 4.6.812.1.2Stephen Finucane2020-07-231-2/+9
| | | | | | | | | | | | | | The 'kombu.connection.Connection.ensure_connection' method has changed from calling 'retry_over_time' on 'self.connect' to calling it on 'self._connection_factory' [1], meaning our mocks are outdated. Address this change. [1] https://github.com/celery/kombu/pull/1193/commits/398aa5b8cd1fe1fc Change-Id: Ibbcf21a57ab1e3f90c21901296e5c088b645127c Signed-off-by: Stephen Finucane <sfinucan@redhat.com> Closes-Bug: #1885923 (cherry picked from commit afb035d97185fa9c622bdb9b4c31c71f01160370)
* Simplify tools/test-setup.shAndreas Jaeger2020-07-023-39/+22
| | | | | | | | | | | | | | | | | | | | test-setup.sh is called after bindep is run in CI, and tox is not setup. Simplify the script so that it only does what's needed - install qdrouterd for Ubuntu from qpid/testing. Install the other packages using bindep, add test to amqp1 profile. Add amqp1 to bindep_profiles where needed for scenario tests, previously test-setup.sh added it everywhere. NOTE(elod.illes): skip annotation removed from test_impl_rabbit.py, as kombu is constrained in ussuri with the version that does not need any test to skip. Change-Id: Ic3a9e2c873619670edfbf71022d593f3cb5f70f2 Related-Bug: #1885923 (cherry picked from commit 7e406c312a6514e7ae377edb52b9e02b5bf37a7d)
* Print warning message when connection running out12.1.1shenjiatong2020-05-291-0/+4
| | | | | | | | | | | I believe when connection pool running out of available resources, there will be all kinds of weird consequences following. So let's print warning logs when we are going to waiting indefinitely for the lock Change-Id: I5ca930cada523bc77c644703a0f02b9160816231 Related-bug: #1871813 (cherry picked from commit 96300a32213d1a9bf114b90bef6971d69b839d1d)
* Update TOX/UPPER_CONSTRAINTS_FILE for stable/ussuriOpenStack Release Bot2020-04-141-1/+1
| | | | | | | | | | | | 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: Icde5163e169fba2831a024f6f3b8c39fc35cf44d
* Update .gitreview for stable/ussuriOpenStack Release Bot2020-04-141-0/+1
| | | | Change-Id: I08173d81f59c3470a8322dbe6ea110544ac649b4
* Update hacking for Python312.1.0Andreas Jaeger2020-03-3011-40/+50
| | | | | | | | | | | | | | | | | | | The repo is Python 3 now, so update hacking to version 3.0 which supports Python 3. Update local hacking check for new flake8 version. Blacklist: W504 line break after binary operator Fix: E741 ambiguous variable name E117 over-indented E305 expected 2 blank lines after class or function definition, found 1 F841 local variable 'e' is assigned to but never used W605 invalid escape sequence '\.' Change-Id: I99d574ca6569f1f177d2c5ce1011f269f4343619
* Merge "Setup backend scenarios for functional tests"12.0.0Zuul2020-02-218-163/+178
|\
| * Setup backend scenarios for functional testsAndy Smith2020-02-058-163/+178
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patchset introduces scenarios for the functional tests to unify the setup and configuration of alternate messaging backends for RPC and Notifications. The scenarios are defined to reduce redundancy in the testing of backends and to demonstrate functional correctness across driver combinations. Current driver support: rabbit - RPC, Notify amqp - RPC kafka - Notify RPC Notify --------- ---------- scenario01 rabbit rabbit scenario02 rabbit kafka scenario03 amqp rabbit scenario04 amqp kafka It is anticipated that additional scenarios will be defined as new drivers are introduced and/or new messaging intermediarites are supported. Note: The removal of python2 jobs are also included patch Change-Id: I0f86416623a0b718516147f0660b4df2b74cf867
* | Remove the deprecated blocking executorHervé Beraud2020-02-188-58/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | The blocking executor has been deprecated in Pike and marked for removal in Rocky, but some user like Mistral asked us to wait before. We decided to remove this executor for Train or next cycle, now we are in the Ussuri and after some researchs on usage I think we can go ahead. This patch drop the deprecation warnings, related unit tests and set the server with the threading executor is the default executor. Change-Id: If07bab61ee2b148658b88be98b12f8539f274efe Closes-Bug: #1715141
* | remove outdated headerHervé Beraud2020-02-101-1/+0
| | | | | | | | Change-Id: I1ac92354fea2a70e5fe72a0e3b48d4c435b5286d
* | reword releasenote for py27 support droppingHervé Beraud2020-02-061-1/+1
|/ | | | Change-Id: Ic65842371eac32cec3a7b66cb6aa0f3ef52b8637
* [ussuri][goal] Drop python 2.7 support and testing11.0.0Hervé Beraud2020-02-037-67/+12
| | | | | | | | | | | | | | OpenStack is dropping the py2.7 support in Ussuri cycle. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html Change-Id: I15cc79159b603e232e442e202c78d6c56dc73252
* Merge "Add support for kafka SSL autentication"Zuul2020-01-304-3/+39
|\
| * Add support for kafka SSL autenticationMichal Arbet2020-01-164-3/+39
| | | | | | | | Change-Id: Idef066a2e3b4923789a6b081d5442e931aba4507
* | Don't log NoSuchMethod for special non-existing methodsOleg Bondarev2020-01-232-3/+14
|/ | | | | | | | Such non-existing methods are used as health probes. Please see bug for details. Change-Id: I8f6b4a669ec11721f76cf03abcd7d802c3c11eb5 Closes-Bug: #1857319
* Merge "Adding debug logs on AMQPListener poll"Zuul2020-01-151-0/+8
|\
| * Adding debug logs on AMQPListener pollHervé Beraud2020-01-141-0/+8
| | | | | | | | | | | | | | | | Adding some debug logs to track execution on the AMQPListener poll function to observe if workers incoming messages are dispatched to workers and if listener is stuck. Change-Id: Ia9b9ef62b0b59c78283c6a8cc5b7ce42282e73b5
* | tox: Trivial cleanupHervé Beraud2020-01-081-15/+3
| | | | | | | | | | | | Move 'basepython' to the top-level 'testenv'. Change-Id: I13e72ec6cbd006ca6eccfe21f2a0584e86a52669
* | Merge "Ignore releasenote cache within git untracked files"10.5.0Zuul2019-12-191-0/+2
|\ \
| * | Ignore releasenote cache within git untracked filesHervé Beraud2019-12-181-0/+2
| | | | | | | | | | | | Change-Id: If616ac023f578f073d9ae8596bc8ce870096ef0b
* | | Merge "Remove telemetry checks"Zuul2019-12-194-245/+0
|\ \ \
| * | | Remove telemetry checksAndy Smith2019-12-024-245/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The telemetry tests are not actively maintained and have been failing checks for quite some time. Remove the non-voting tests for now and plan to introduce new tests in the future for better coverage of notifications. Change-Id: I6c30c28ee4c8be4677ccecf8822af15b060cf804
* | | | Merge "Do not use threading.Event"Zuul2019-12-1811-31/+40
|\ \ \ \ | |_|/ / |/| | |
| * | | Do not use threading.EventJohn Eckersberg2019-12-1811-31/+40
| | |/ | |/| | | | | | | | | | | | | | | | | | | Waiting on a threading.Event with eventlet can cause busy looping via epoll_wait, see related bug for more details. Change-Id: I007613058a2d21d1712c02fa6d1602b63705c1ab Related-bug: #1518430
* | | Merge "Removed unused variable pools"Zuul2019-12-181-2/+0
|\ \ \ | |/ / |/| |
| * | Removed unused variable poolsChenjun Shen2019-12-181-2/+0
| | | | | | | | | | | | Change-Id: I8f3a22d2af3f34b368bae3465bf8433fe2d3e22b
* | | Revert "Add RPC incoming and reply log"10.4.1Kenneth Giusti2019-12-093-21/+1
| |/ |/| | | | | | | | | | | | | | | | | This broke non-rabbitmq message bus drivers. See: https://bugs.launchpad.net/oslo.messaging/+bug/1855775 This reverts commit b104f254ab43d5e2589e845eff84b1bd096cb42d. Change-Id: I17a448a768b544482b375b0076889db989e03e8c
* | Migrate grenade jobs to py310.4.0Ghanshyam Mann2019-11-192-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As part of community goal of dropping py27 support[1], we are moving the devstack to py3 by default[2]. That will make grenade job to perform upgrade from py2 to py3 which will not work (we have seen the failure in neutron-grenade job). To avoid existing grenade py2 job break, this commit moves grenade jobs to py3 which is what we planned as part dropping the py2 support. [1] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html [2] https://review.opendev.org/#/c/649097/12 http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010938.html Change-Id: I128827b77ed791ea0084008cdecbd7ac37fa9079
* | Make sure minimum amqp is 2.5.2Eyal2019-11-182-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | amqp fixed a bug in 2.5.2 that is needed also update kombu to support amqp 2.5.2 see https://review.opendev.org/#/c/693704/ https://github.com/celery/py-amqp/commit/86cb254dceab75e0240b4fa6b97249de70036a4b Change-Id: I4b72d8feb85c2b9b4657510c356cd21e22fe40c2 Closes-bug: #1852058
* | Merge "Switch to Ussuri jobs"Zuul2019-11-121-1/+1
|\ \
| * | Switch to Ussuri jobspengyuesheng2019-10-241-1/+1
| |/ | | | | | | Change-Id: I4297685cbe5c5ec71b68467a54746c2f4814f104
* | Merge "Add RPC incoming and reply log"Zuul2019-11-123-1/+21
|\ \
| * | Add RPC incoming and reply logLIU Yulong2019-10-213-1/+21
| |/ | | | | | | | | | | | | | | | | Typically a simple log will not narrow down the performance, but give us more information about the service status. Change-Id: I51c8f2743dd39cccd3d1d021d3c50dc09f70cd97 Closes-Bug: #1847747
* | Merge "tox: Keeping going with docs"Zuul2019-11-113-5/+11
|\ \
| * | tox: Keeping going with docscaoyuan2019-10-243-5/+11
| |/ | | | | | | | | | | | | | | | | | | | | | | Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name suggests, keeps the build running when it encounters non-fatal errors. This is exceptionally useful in avoiding a continuous edit-build loop when undertaking large doc reworks where multiple errors may be introduced. [1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045 Change-Id: If9885a1f064226909181d8b69241eb814deb2105
* | Merge "Modify some comments to make them clickable"Zuul2019-11-041-3/+3
|\ \
| * | Modify some comments to make them clickableHervé Beraud2019-10-111-3/+3
| |/ | | | | | | Change-Id: Ib085fa551950f1c1461a11bb80f4909fb8425484
* | Remove unused variable WAKE_UP10.3.0Chenjun Shen2019-10-291-2/+1
|/ | | | | Change-Id: I65f57973b66f353a1e6fef3d0bf7793f821c1c5c Closes-Bug: 1850259
* Merge "Update master for stable/train"Zuul2019-10-102-0/+7
|\
View Lorry Controller Status