summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Don't log non-db error in retry wrapper"4.3.1Jenkins2016-01-202-5/+12
|\
| * Don't log non-db error in retry wrapperMatt Riedemann2016-01-132-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 838e314a21fef9ca6cf99140b2400e0d3b68b109 changed the retry wrapper code to not log exception traces for expected errors, like when retrying on a DBDeadlock. It did, however, log an unexpected exception but was not checking the type, like in the case of a nova OverQuota exception. Since _is_execption_expected already logs at debug level an expected DB error, like DBDeadlock, during a retry loop, we don't need to log it again. And if the exception is unexpected, like OverQuota from nova, then we shouldn't trace that exception in the retry loop before reraising but instead just let the caller handle it. Adds a unit test to make sure that nothing is logged in the unexpected exception case during the retry loop. Co-Authored-By: Sean Dague <sean@dague.net> Change-Id: Ic3e45029378dc96ce01398d9b55f51e20ef08189 Closes-Bug: #1532880
* | Imported Translations from ZanataOpenStack Proposal Bot2016-01-1713-97/+100
| | | | | | | | | | | | | | For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I73c4b3c1a9893779d3526ad048e09a76f870321f
* | Updated from global requirementsOpenStack Proposal Bot2016-01-172-20/+20
| | | | | | | | Change-Id: I94f7328437266d6dbaece5e6b2f21a0ea700064e
* | Fix tests to work under both pymsysql 0.6.2 and 0.7.xDavanum Srinivas2016-01-151-3/+8
|/ | | | | | | | | | | | | | | | | | | | In 0.6.2, the exc.statement and exc.params were as follows: exc.statement = {unicode} u'INSERT INTO resource_entity (id, foo_id) VALUES (%s, %s)' exc.params = {tuple} (1, 2) In 0.7.1, the exc.statement and exc.params are as follows: exc.statement = {unicode} u'INSERT INTO resource_entity (id, foo_id) VALUES (%(id)s, %(foo_id)s)' exc.params = {dict} {'id': 1, 'foo_id': 2} So the easiest thing to support both is to use string interpolation and then check if they are equal. This approach works for both py34 and py27 as well. Note that we still have to test the old way for sqlite which has (?, ?) in the SQL statement. Closes-Bug: #1533861 Change-Id: Iab9f0e4b4dd337363dd7e705c1155f3f6517b404
* Updated from global requirements4.3.0OpenStack Proposal Bot2016-01-061-2/+2
| | | | Change-Id: Ic7ab3b9e6dc8354861be1af46210269f74c04333
* Merge "Put py34 first in the env order of tox"Jenkins2015-12-291-1/+1
|\
| * Put py34 first in the env order of toxJanonymous2015-12-221-1/+1
| | | | | | | | | | | | | | | | | | | | To solve the problem of "db type could not be determined" on py34 we have to run first the py34 env to, then, run py27. This patch puts py34 first on the tox.ini list of envs to avoid this problem to happen. Change-Id: I2365f66eee43cd36e62fe05e582c328787a0a112 Closes-bug: #1489059
* | Updated from global requirementsOpenStack Proposal Bot2015-12-211-1/+1
|/ | | | Change-Id: I6d23bee6e6e9b0a7a6dcb20edb8ef4476c2d561e
* Fix comparison of Variant and other type in compare_type4.2.0AKamyshnikova2015-12-192-1/+18
| | | | | | | | | Neutron hit problem with comparison Variant type and BigInteger. Seems that comparison with Variant is not done properly so add correction of it in compare_type. Change-Id: Ic5279fcf11cf9123d007010d094a7f255ba0555e Related-bug: #1526675
* Updated from global requirementsOpenStack Proposal Bot2015-12-151-1/+1
| | | | Change-Id: I1f3e785a9e7344279c2d4176f67678be564169d1
* Updated from global requirementsOpenStack Proposal Bot2015-12-111-1/+1
| | | | Change-Id: I37020a0bfbcd19a99af5a9b090d81d60fee54d74
* Don't trace DB errors when we're retryingMatt Riedemann2015-12-081-1/+6
| | | | | | | | | | | | | | | | | | | | If we know we're retrying on DB failures, let's be smarter and not trace an exception at ERROR level while looping, since this clutters up the logs and causes confusion when trying to track down failures. DBDeadlock errors show up quite a bit in q-svc and n-api logs in gate runs but when you check logstash for those, they are primarily in jobs that are successful, so the trace is on the first try in the loop and then we pass on the second try - but the trace itself is confusing while debugging gate failures. So let's just be smarter and log at debug level between retries, and if we hit an unexpected exception, log that error (as before), and raise it up to the caller. Closes-Bug: #1523990 Change-Id: I15b4a9b5c7ec9bfede9ec9989de02c1da46eac81
* Merge "Trival: Remove 'MANIFEST.in'"Jenkins2015-12-081-6/+0
|\
| * Trival: Remove 'MANIFEST.in'ChangBo Guo(gcb)2015-12-051-6/+0
| | | | | | | | | | | | | | | | | | Everything in this file is automatically generated by pbr. There appears to be no good reason to keep it around. More details please see: https://github.com/openstack-dev/pbr/blob/master/pbr/packaging.py#L384 Change-Id: I48e3a0129949747759acb68984f1e0425185e032
* | Merge "Remove iso8601 in requirements.txt"Jenkins2015-12-081-1/+0
|\ \
| * | Remove iso8601 in requirements.txtChangBo Guo(gcb)2015-12-051-1/+0
| |/ | | | | | | | | | | We don't use it in anywhere. Change-Id: I411755e8297459b9b726cb7235da08236d098455
* | Updated from global requirementsOpenStack Proposal Bot2015-12-061-1/+1
|/ | | | Change-Id: Ic4ffc33e2b1d4228af88cf952a3f8c129a4db3be
* Refactor deps to use extras and env markers4.1.0Robert Collins2015-11-303-30/+32
| | | | | | | | | | | | Adds extras for e.g. nova to use for testing, so that oslo.db can control the libraries used. Removes test-requirements.txt - it becomes a single env-marker controlled list, and shows how tox will access those dependencies. Co-Authored-By: Roman Podoliaka <rpodolyaka@mirantis.com> Change-Id: I97ef5bad215abe60d92c3fda4474c48ccb13eab0
* Added allow_async propertyPavel Kholkin2015-11-262-6/+84
| | | | | | | | | In Nova we need a decorator that is READER by default but can be used as ASYNC if asynchronous session is started before. Co-Authored-By: Sergey Nikitin <snikitin@mirantis.com> Change-Id: I0c0f332d87bf6b1213c800763918340b1e226934
* Updated from global requirements4.0.0OpenStack Proposal Bot2015-11-192-3/+3
| | | | Change-Id: If775c65d34d99a93a7e56de9dfb1f017f8b9216f
* Remove python 2.6 classifierChangBo Guo(gcb)2015-11-171-1/+0
| | | | Change-Id: I8d17187229811cdb9fc7a89f2f58726bdb96db4e
* Remove python 2.6 and cleanup tox.iniDavanum Srinivas2015-11-161-8/+1
| | | | | | | | | | | | | * Remove support for python 2.6 * Remove skipsdist : Needs to be set only if sdist is expensive * Remove usedevelop : only needed when skipsdist is set to True * Remove install_command : We can just use the default, we don't need to override * sitepackages : default is already false Change-Id: I12de2f2175fce3a0b24c16a1fc55100c2927883f
* Detect not-started _TransactionFactory in legacy3.2.0Mike Bayer2015-11-112-0/+32
| | | | | | | | | | | | | When LegacyEngineFacade is passed a _TransactionFactory that is not started, or one that fails to start, the _start() method should be called again each time the factory is called upon; this ensures that the failed start either can be made to succeed, or at least re-raises the same error as earlier, instead of falling into attribute access for non-existent attributes. Change-Id: I7484f837d455c1f69c448e5ccadc277d19af47e7 Closes-Bug: #1515326
* Added method get_legacy_facade() to the _TransactionContextManagerSergey Nikitin2015-11-112-1/+24
| | | | | | | | | | | | This public method was added to be able to create several legacy facades from several transaction context managers. It could be used in Nova where we have two DBs. There we need some legal way to create two legacy facades because right now in Nova we create facades by using private field _factory. It is not quite right. Change-Id: I96b3dbcbc5a05ac025c247ae6d8abfc988d0295e
* Removed Unused variable 'drivertype'nandal2015-11-091-1/+1
| | | | | | Fixes bug #1514399 Change-Id: I06154bdafb2be6d5ae65fc9d51c0dc7fafcaa8aa
* Updated from global requirementsOpenStack Proposal Bot2015-10-231-1/+1
| | | | Change-Id: Ia390b2d2065f2db197dc4e3b87a71b1d1125f481
* Imported Translations from ZanataOpenStack Proposal Bot2015-10-2313-81/+62
| | | | | | | For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I2c99373229cef3a536039f1116c2414cde4b9d17
* Updated from global requirementsOpenStack Proposal Bot2015-10-191-1/+1
| | | | Change-Id: I40e63dfa3051e765fa5e48adb5e79895fec98566
* Updated from global requirements3.1.0OpenStack Proposal Bot2015-10-161-1/+1
| | | | Change-Id: Iab02eb57514254f3f5f18116b3e0fd2904c1224d
* Merge "Add debug logging for DB retry attempt."Jenkins2015-10-151-0/+3
|\
| * Add debug logging for DB retry attempt.Eugene Nikanorov2015-10-121-0/+3
| | | | | | | | | | | | | | | | That should help to debug DB contentions. Right now it's not clear from the logs if or how often reconnects are triggered. Change-Id: I8c9c95c262e69d9aa97294abe7fbfb31b1b18c5d
* | Updated from global requirementsOpenStack Proposal Bot2015-10-131-1/+1
| | | | | | | | Change-Id: I7ce9fd2785bad9b3f6870288d2e47ffdae60f970
* | Merge "Fix the home-page value with Oslo wiki page"Jenkins2015-10-131-2/+2
|\ \
| * | Fix the home-page value with Oslo wiki pagevenkatamahesh2015-09-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The current value for home-page is launchpad url which is not relevant one and so it is replaced with Oslo wiki page Change-Id: I202d9eb72f7ea152e8ed10b86556b334f7793b34
* | | Merge "Fix coverage configuration and execution"3.0.0Jenkins2015-10-092-3/+4
|\ \ \
| * | | Fix coverage configuration and executionRonald Bradford2015-10-082-3/+4
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | A number of configuration errors prevent the successful creation of code coverage. This corrects the .coveragerc source/omit setup and the tox package name generation. http://lists.openstack.org/pipermail/openstack-dev/2015-October/076193.html Change-Id: I677ca6ed73096cf408455cd0968a488a1cbab636
* | | Merge "No need for Oslo Incubator Sync"Jenkins2015-10-081-4/+0
|\ \ \
| * | | No need for Oslo Incubator SyncDavanum Srinivas2015-10-041-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We can remove openstack-common.conf as we don't sync any code from oslo-incubator any more. Change-Id: I37149764b28791f5dc8c82ecefcb14fd75a57dfa
* | | | Merge "Add universal wheel tag to setup.cfg"Jenkins2015-10-081-0/+3
|\ \ \ \
| * | | | Add universal wheel tag to setup.cfgDavanum Srinivas2015-10-041-0/+3
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | This project is 2 and 3 compatible so a universal wheel is appropriate/expected. Change-Id: Ide29cc4b33a8be94459babbaecb638b9b17b04d7
* | | | Merge "Correct invalid reference"Jenkins2015-10-081-1/+1
|\ \ \ \ | |/ / / |/| | |
| * | | Correct invalid referenceBrant Knudson2015-09-281-1/+1
| |/ / | | | | | | | | | | | | | | | | | | There's no oslo_db.migration module. It's an entrypoint group name. Therefore it should not be using :mod:. Change-Id: I14f26c1a9ae1bd6b5b1154b3f49eb9e1518cafc3
* | | Updated from global requirementsOpenStack Proposal Bot2015-10-021-1/+1
|/ / | | | | | | Change-Id: I18558198038f6e674276166c7c05b4ada690ce29
* | Imported Translations from ZanataOpenStack Proposal Bot2015-09-268-34/+40
| | | | | | | | | | | | | | For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I1ac5df90739f1421adb67409e726f1b258ee9383
* | Merge "Use stevedore directive to document plugins"Jenkins2015-09-253-8/+17
|\ \
| * | Use stevedore directive to document pluginsAllison Randal2015-09-253-8/+17
| | | | | | | | | | | | | | | | | | | | | Add directives to the documentation to bring in the docstrings from the plugins. Change-Id: I2afe1d1e4a9abfa1d3cdf85bc4008ff8f772123c
* | | Merge "Change ignore-errors to ignore_errors"Jenkins2015-09-251-1/+1
|\ \ \ | |/ / |/| |
| * | Change ignore-errors to ignore_errorsMonty Taylor2015-09-211-1/+1
| | | | | | | | | | | | | | | | | | Needed for coverage 4.0 Change-Id: I5e22c72ba110f3e52c719ca7b2b0547ef4f1dccc
* | | Merge "Make readme and documentation titles consistent"Jenkins2015-09-252-12/+12
|\ \ \
View Lorry Controller Status