summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Cap Bandit below 1.6.0 and update Sphinx requirementpike-eolstable/pikeKenneth Giusti2021-03-203-4/+9
| | | | | | | | | | | | | | | | | | | | | Bandit 1.6.0 accidentally changed how the exclusion list option is handled and breaks our use of it. Cap to the previous version until Bandit has fixed the problem. Sphinx 2.0 no longer works on python 2.7, so we need to start capping it there as well. NOTE(elod.illes): use upper-constraints.txt for docs tox target, to limit dulwich to the version that was used in stable/pike. Also install the content of requirements.txt otherwise those will be installed unconstrained during the test run. Conflicts: doc/requirements.txt Change-Id: Ie6b379f2c99862c37891ac03c52464e07bc2b2cc (cherry picked from commit 4f467fbd73092aadda8b42e517bb60a4782064ae) (cherry picked from commit 012cdcd03a65da90d8aa36b2afc51e778957cc12)
* OpenDev Migration PatchOpenDev Sysadmins2019-04-191-1/+1
| | | | | | | | | | | | | | | This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
* Add release note for amqp library TLS/SSL errorpike-em5.30.8Kenneth Giusti2019-02-221-0/+17
| | | | | Change-Id: I90c172d673084ff0cb0a3dd0fae21a5d62d35286 Related-Bug: #1800957
* Do not access the connection's socket during error callback5.30.7Kenneth Giusti2018-09-261-5/+9
| | | | | | | | | | | | | | | | The _get_connection_info() method attempts to gather debug information from the connection, and will reach into the amqp channel to get the local (client's) TCP port number via the 'sock' property. If _get_connection_info() is called from autoretry's on_error handler the 'sock' property notices that the transport is not set and attempts to re-connect. amqp has deprecated this reconnect behavior, and in any case the client's socket is irrelevant since the connection may not be valid at this point. Closes-Bug: #1745166 Change-Id: I3c42f8463605927f6f94d6c3a7f05e584476abc1 (cherry picked from commit 361669764fd28b4f6d5f1c6896624f2da4ff5151)
* Avoid logging passwords on connection events5.30.65.30.5Kenneth Giusti2018-08-271-1/+3
| | | | | | Change-Id: I15c8c4a1177c363283281d2fed63545658eda5de Closes-Bug: #1787214 (cherry picked from commit d9866029a2aab2c5f001100813c0425b4905fdf6)
* import zuul job settings from project-configDoug Hellmann2018-08-031-0/+12
| | | | | | | | | | | | | | | This is a mechanically generated patch to complete step 1 of moving the zuul job settings out of project-config and into each project repository. Because there will be a separate patch on each branch, the branch specifiers for branch-specific jobs have been removed. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I0b329814ee4833f315214213c0d72ee927ca7e7d Story: #2003250
* Suppress excessive debug logs when consume rabbit5.30.4Zhen Qin2018-07-131-5/+4
| | | | | | | | | | | | | | | | | | | | If using rabbitmq as rpc backend, oslo.messaging generates large amount of redundant timeout debug logs (several logs per second on multiple openstack services, such as nova, heat, cinder), in format of 'Timed out waiting for RPC response: Timeout while waiting on RPC response - topic: "<unknown>", RPC method: "<unknown>" info: "<unknown>'. It's because each socket timeout exception is raised to multiple levels of error recovery callback functions then logged repeatedly. However, the accompanying value of socket.timeout exception is currently always “timed out”. Besides, oslo.messaging has implemented retry mechanism to recover socket timeout failure. Therefore, IMO those logs should be suppressed, even if at debug level, to save disk space and make debugging more convenient. Change-Id: Iafc360f8d18871cff93e7fd721d793ecdef5f4a1 Closes-Bug: #1714558 (cherry picked from commit 147186c7b4aabd2155f58f61913882f7a066bcbc)
* Revert "rabbit: Don't prefetch when batch_size is set"5.30.3Wonil Choi2018-05-091-6/+0
| | | | | | | | | | | | | | | | | This reverts commit c881baed29db49c5710795496cb07907e35ceaba. Eventhough batch_size is set, rabbitMQ prefetch count is not changed at the first time of connection creation. It works only connection reset cases(i.e. rabbitMQ restart). So this patch can not fix original issue https://bugs.launchpad.net/ceilometer/+bug/1551667 Moreover, it makes another bug that messages of sameple queues are not consumed properly. So revert it. Change-Id: Ia8ebee8e2a670e46b6a68859bc30e717bd56ed7e Signed-off-by: Wonil Choi <wonil22.choi@samsung.com> Closes-bug: 1759755 (cherry picked from commit e0e8a1ea68bcc33d1a07361102eb87d0cfdd94a9)
* Use stable branch for upper constraintsSean McGinnis2018-01-081-2/+2
| | | | | | | Backporting of upper constraint check missed adding the stable branch to the URL. Change-Id: I30f4ae092027560b4980964bda7f9869aa5d3a45
* Create doc/requirements.txtKenneth Giusti2017-12-292-0/+14
| | | | | | | | | | | | | For compliance with the Project Testing Interface as described in: https://governance.openstack.org/tc/reference/project-testing-interface.html Refer to: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124815.html Change-Id: I3d8c70f66931c15247b530ff7e1c89bfc753446f (cherry picked from commit c7cc6d0742d989f0498bcfa13d362a1421e2d12a)
* Avoid tox_install.sh for constraints supportAndreas Jaeger2017-12-292-36/+9
| | | | | | | | | | | | We do not need tox_install.sh, pip can handle constraints itself and install the project correctly. Thus update tox.ini and remove the now obsolete tools/tox_install.sh file. This follows https://review.openstack.org/#/c/508061 to remove tools/tox_install.sh. Change-Id: Ifaaf656effff20ef08214f111645a3b5fc8b4d28 (cherry picked from commit d68b53f0568afcc171f0f773469a023c11fe3079)
* rabbitmq: don't wait for message ack/requeue5.30.2Mehdi Abaakouk2017-11-302-16/+16
| | | | | | | | | | | | | | | I don't see any obvious reason why we should wait ack/requeue is done. This waiter have already be removed from amqp1. https://git.openstack.org/cgit/openstack/oslo.messaging/tree/oslo_messaging/_drivers/amqp1_driver/controller.py#n242 So, this change remove it from rabbitmq driver too. Closes-bug: #1734788 Change-Id: I5ecedc762596181be19410b863851a0054fd6579 (cherry picked from commit c38857e1101027a734a35f4e80bc4084fabc034b)
* Catch socket.timeout when doing heartbeat_checkVincent Untz2017-11-221-1/+2
| | | | | | | | | | | | heartbeat_check in kombu.connection is not reraising exceptions as exceptions.OperationalError, and the socket timeout during the heartbeat check is really an issue seen in the field when a node goes down; the heartbeat thread just tries again and again to deal with it, without success. Change-Id: I26dbdb18a7e64946db2cba676764ff2d428c7897 Closes-Bug: #1657444 (cherry picked from commit 8bfc3637a25a29583b1e0625c78bf159ac878259)
* Add support for virtual hosts5.30.1Kenneth Giusti2017-09-116-58/+243
| | | | | | | | | | | | | | | | | | | | | Adds the 'pseudo_vhost' option which when enabled will incorporate the virtual host into the address semantics. This creates a 'subnet' like address space for each virtual host. Use this when the messaging bus does not provide virtual hosting support. It is enabled by default as to date none of the supported AMQP 1.0 message buses natively support virtual hosting. It also updates SSL support: SSL can either use the connection hostname or the vhost name when validating a server's certificate. This is controlled by the 'ssl_verify_vhost' option. This option is disabled by default as it requires both vhost and SNI support from the server. By default SSL will use the DNS name from the TransportURL. Change-Id: I49bb99d1b19e8e7e6fded76198da92ca5f7d65ab Closes-Bug: #1700835 Partial-Bug: #1706987 (cherry picked from commit 263dce9ea8e52632cc07d101d1859034eb3943c7)
* Merge "Update UPPER_CONSTRAINTS_FILE for stable/pike" into stable/pikeJenkins2017-08-121-1/+1
|\
| * Update UPPER_CONSTRAINTS_FILE for stable/pikeOpenStack Release Bot2017-07-281-1/+1
| | | | | | | | Change-Id: Ifb203f8eac75d35d803f4412b7e65ccb5f5d8c43
* | Updated from global requirementsOpenStack Proposal Bot2017-08-111-1/+1
| | | | | | | | Change-Id: I2d5b758c8d391e57848479622b0c9417c4da739d
* | Merge "Update .gitreview for stable/pike" into stable/pikeJenkins2017-08-051-0/+1
|\ \ | |/
| * Update .gitreview for stable/pikeOpenStack Release Bot2017-07-281-0/+1
| | | | | | | | Change-Id: Ic7fb36ede56033c9b97342e7ba6ea9797c54dbda
* | Remove the test that counts kombu connect callsKenneth Giusti2017-08-041-6/+1
|/ | | | | | | | | | | | | | | | This test removes a check of the number of times kombu's Connection.connect() method is being called for each mocked retry. The number of calls kombu makes internally is irrelevant to proving the API is correct. The rest of the tests do ensure that the target method is retried as expected, which is relevant to the API. This change is necessary due to the kombu v4.1.0 release actually calling Connection.connect() twice for each call to the target method when compaired to earlier releases. Change-Id: I3326b8e92efe3bef00b1f389d81944af9cc080f8 Closes-Bug: #1707263 (cherry picked from commit 2c9ac202ebeaf0fca3316a3231d75d86718a97cf)
* Updated from global requirements5.30.0OpenStack Proposal Bot2017-07-181-1/+1
| | | | Change-Id: I7b81c8def55f702b95204d727b95d879c441167e
* Merge "Add monkey_patch to demo code."Jenkins2017-07-131-0/+7
|\
| * Add monkey_patch to demo code.zhiCHang19902017-07-111-0/+7
| | | | | | | | | | | | | | | | The RPC server code can not work if we don't add eventlet.monkey_patch() at the begining. Change-Id: I65a162a427fb5615c95a70e6d1bbec899a78f231
* | Update URLs in documents according to document migrationChangBo Guo(gcb)2017-07-125-6/+6
| | | | | | | | Change-Id: I139d4d38e49590d50e51495b6e3b84836975c6ed
* | Merge "switch from oslosphinx to openstackdocstheme"5.29.0Jenkins2017-07-103-13/+21
|\ \
| * | switch from oslosphinx to openstackdocsthemeDong Ma2017-07-063-13/+21
| |/ | | | | | | Change-Id: Ic3d9b9cbef0040512e37c8e99df7bb028e344bc9
* | update the docs url in the readmeDong Ma2017-07-061-1/+1
|/ | | | Change-Id: I9e24fe1c1dd17246fd090e852b5895132952eb02
* Merge "rearrange content to fit the new standard layout"Jenkins2017-07-0629-24/+71
|\
| * rearrange content to fit the new standard layoutDong Ma2017-07-0629-24/+71
| | | | | | | | | | Change-Id: I4dd1c9c289d31077b71f3d96877b776d9d5e16f7 Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
* | Merge "Enable some off-by-default checks"Jenkins2017-07-051-0/+1
|\ \ | |/ |/|
| * Enable some off-by-default checksblue552017-06-221-0/+1
| | | | | | | | | | | | | | | | Some of the available checks are disabled by default, like: [H106] Don’t put vim configuration in source files [H203] Use assertIs(Not)None to check for None Change-Id: I54b4b950dfcd2ce5a64f38b5d5b5cbe95846a8fa
* | Updated from global requirementsOpenStack Proposal Bot2017-06-271-1/+1
|/ | | | Change-Id: I3c492ddd176882989a8a083fb560ab5c5df2452f
* Updated from global requirements5.28.0OpenStack Proposal Bot2017-06-151-1/+1
| | | | Change-Id: Ib872e230f563ca2e1e3e67f9dabe13250735c9e7
* Add kafka_driver directoryAndrew Smith2017-06-135-3/+3
| | | | | | Make uniform with other drivers, kafka driver files, etc. Change-Id: I6c6e201c304a6005ef191f96e5ac39ffaf4ab8f7
* Merge "Fix html_last_updated_fmt for Python3."Jenkins2017-06-121-2/+1
|\
| * Fix html_last_updated_fmt for Python3.ZhangHongtao2017-06-091-2/+1
| | | | | | | | | | | | | | | | | | html_last_updated_fmt option is interpreted as a byte string in python3, causing Sphinx build to break. This patch makes it utf-8 string. Change-Id: Ifde17e94d0345a289eea29ba3d664d31f1eb51d9 Closes-Bug:#1693670
* | Updated from global requirements5.27.0OpenStack Proposal Bot2017-06-101-1/+1
| | | | | | | | Change-Id: I9313f1d68f67c3839a261ac9661e85bbdb03b94e
* | Merge "Fix rabbitmq driver with blocking executor"Jenkins2017-06-092-3/+29
|\ \
| * | Fix rabbitmq driver with blocking executorMehdi Abaakouk2017-06-082-3/+29
| |/ | | | | | | | | | | | | | | | | | | | | | | | | We recently move ack/requeue of messages in main/polling thread of rabbitmq drivers. And break the blocking executor. This one is not tested by any tests and now deprecated. This change workaround the issue until we completely remove the blocking executor. Change-Id: Id479100f6ff364cf67a199e9b70f9f0c7bf7e1a9 Closes-bug: #1694728
* | Add note for blocking executor deprecationThomas Herve2017-06-081-0/+6
|/ | | | Change-Id: I5a7607add852258ca6623f9b855c36eda5ff9e1e
* Build universal wheelsJeremy Stanley2017-06-071-0/+3
| | | | | | | | The trove metadata for this package claims to support both Python 2.x and Py3K; build universal wheels so Python 3.x interpreters can consume them too. Change-Id: I0b88fcaa2ea36e1d7478d76b86c6c1f1e68c8616
* Merge "Updated from global requirements"Jenkins2017-06-061-1/+1
|\
| * Updated from global requirementsOpenStack Proposal Bot2017-06-061-1/+1
| | | | | | | | Change-Id: I8f6d464a259ce1afc83728ddced8e8803e04f657
* | Merge "deprecated blocking executor"Jenkins2017-06-065-46/+54
|\ \ | |/ |/|
| * deprecated blocking executorMehdi Abaakouk2017-06-045-46/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Using blocking executor is not recommended for application. But it looks like some use it just because it's the default and are not aware their should change it despite of documentation and logging message. Choosing the application threading model is an important step of an application. This change deprecates it, in the future we will just make executor mandatory. This will ensure that application make a choice. Also this will reduce headache of oslo.messaging developers to make the driver code working in a sync and async. And to finish test coverage of blocking executor is 0%... This rework some tests to remove logging.captureWarnings() that can catch unwanted warning of other tests. Tests mocks warning instead. Related-bug: #694728 Change-Id: Ic67164d12e7a9bed76d6e64ca2ced12e3984ff5f
* | Fix serializer testsKenneth Giusti2017-06-051-4/+4
|/ | | | | | | | The serializer tests occasionally fail since the order of a dict() is not guaranteed. Explicitly compute the serializer instead of pre-computing it. Change-Id: I74f8fa227e6508491b5982fe7e2841683724540c
* Merge "Clean up the TransportURL documentation"5.26.0Jenkins2017-06-023-9/+38
|\
| * Clean up the TransportURL documentationKenneth Giusti2017-06-013-9/+38
| | | | | | | | | | | | | | | | Be specific regarding which characters can be used in the 'username' and 'password' fields of the URL. Change-Id: I9a2a801b3dd86fceffb05f4d52c715748c88d0cb Closes-Bug: #1693967
* | Updated from global requirementsOpenStack Proposal Bot2017-06-021-1/+1
| | | | | | | | Change-Id: I1a4a507ba4077b8a8e2e4f1c4e7ac93158918b48
* | Merge "Mark the Pika driver as deprecated"Jenkins2017-05-313-5/+23
|\ \ | |/ |/|
View Lorry Controller Status