summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Prepare for using standard python testsmitaka-eolstable/mitakaAndreas Jaeger2017-02-021-0/+57
| | | | | | | | | | | | | | | | Add simple script to setup mysql and postgresql databases, this script can be run by users during testing and will be run by CI systems for specific setup before running unit tests. This allows to change in project-config the python-db jobs to python-jobs since python-jobs will call this script initially. See also http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html Change-Id: I3463e75057d0d4544f6a0212da888759ab5e171b Needed-By: I92e6e6502c2c516babf2bf66f3514875f77c460e (cherry picked from commit 6bd5974610cd3b77d966dd8ce68117ddbf3a371b)
* Merge "Add missing '_LE' import in trove/cmd/guest.py" into stable/mitaka5.1.2Jenkins2016-09-121-0/+1
|\
| * Add missing '_LE' import in trove/cmd/guest.pyChaozhe.Chen2016-09-121-0/+1
| | | | | | | | | | | | | | | | | | Global name '_LE' was missing in trove/cmd/guest.py. This patch adds this missing import. Change-Id: Ia0b4ecb27f0f4dcae88a56288bc5052f1afa63e8 Closes-Bug: #1620888 (cherry picked from commit e428d76ace2e21d83991243ad00b4951ae05da6a)
* | Skip 'eject valid master' replication testAmrith Kumar2016-09-113-4/+23
|/ | | | | | | | | | | | | | | | | | | | | | | | | There is a test to eject a valid master during replication that is failing more and more often in the scenario tests. Basically the eject will only work if the heartbeat from the current master is more than a minute old. This shouldn't happen in the scenario test run, but it does - quite often. Since this is consuming a large amount of gate resources, and the bug isn't that onerous (but is probably hard to fix), the current 'eject valid master' test will be turned off until the fix lands. The scenario test will print out the bug number during each run as a reminder (using the new SkipKnownBug method). Co-Authored-By: Peter Stachowski <peter@tesora.com> Co-Authored-By: Amrith Kumar <amrith@tesora.com> Author: Peter Stachowski <peter@tesora.com> Change-Id: Ia543da551ad4394d4964541f9db474e0792b9337 Related-Bug: #1622014 (cherry picked from commit 7d8d743d8e168f64fa893c975d7301507d4985d8) Conflicts: trove/tests/scenario/runners/replication_runners.py trove/tests/scenario/runners/test_runners.py
* guest_id missing err, switch config_drive default5.1.1Greg Retkowski2016-09-014-3/+22
| | | | | | | | | | | | | | | | | | | | | | | This changes the default setting for use_nova_server_config_drive from False to True. By default, nova does not use a config drive for launched instances. Therefore trove must implicitly request the config drive be used so that it can inject guest_info.conf into the guest VM. This commit also adds an error to guestagent when guest_id is missing. If the guest_id configuration parameter is not set at guestagent startup it will throw a RuntimeError. This case typically occurs because guest_info.conf was not injected into the guest, or was not included in the set of configs that guestagent reads at startup. And finally, this commit adds a section in the 'building guest images' documentation describing how configuration is injected into the guest agent. Change-Id: I084c841472183893a63ca7b70d560f44a2f08901 Partial-Bug: 1609915 (cherry picked from commit f7b8805c3aed5b5cef01176cc1d9136bd31125fb)
* Updated from global requirementsOpenStack Proposal Bot2016-08-251-1/+1
| | | | Change-Id: Ib505c2d727d06264a8923526eccf7230a7823356
* Use constraints for coverage jobAndreas Jaeger2016-07-181-6/+0
| | | | | | | | | | OpenStack CI supports now constraints in the coverage job - as a first job to check that the recent changes for zuul-cloner work correctly. Use constraints for cover environment. Change-Id: I148a50e3f17fcbf2187898a59b28ea4ed0a827a2 (cherry picked from commit 4ad0dfe88c6362356c8083d167f43ab495da661d)
* added release note for requirement changeAmrith Kumar2016-07-151-0/+4
| | | | | | | | | per review comments in https://review.openstack.org/#/c/340408/, I am adding this release note and will update that commit to reflect the hash once this change merges. Change-Id: I800b9eb1d909ce6efe3a123ec8ad85f1592bfefc Related: If5f39f4a34655a6267df18b3d11450061ec8cbc3
* Updated from global requirements5.1.0OpenStack Proposal Bot2016-06-101-1/+1
| | | | Change-Id: If747e13c9b3923ea46fd72571cf95f8093973cb8
* Merge "Fixed module-apply on removed module" into stable/mitakaJenkins2016-06-013-2/+35
|\
| * Fixed module-apply on removed modulePeter Stachowski2016-05-203-2/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | If you apply a module, remove it and then apply it again it would no longer show up in the module-query command. This has been fixed and corresponding tests added to the module scenario run. Also added missing 'object' to ModuleManager class Closes-Bug: #1571799 (cherry picked from commit I3302a2547cf88f1da1ba4abca6617981572782d4) Change-Id: Idecead4b9f021da16bf1b138718b5169bce01205
* | Unsupported module driver not logged correctlyPeter Stachowski2016-05-252-1/+5
|/ | | | | | | | | | | | If an invalid module driver is found, the method is erroneously printed out instead of the actual 'type.' This is due to missing parenthesis in the logging call. This has been fixed. Change-Id: I6fb23b3dbbec98de9ee1e2731bcfc56ab3c0ca42 Closes-Bug: #1579900 (cherry picked from commit 970d23ff2ae5449786e95b482dff344d4a48b323)
* Merge "Reuse Cassandra connections" into stable/mitaka5.0.1Jenkins2016-05-174-126/+152
|\
| * Reuse Cassandra connectionsPetr Malik2016-05-174-126/+152
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Cache and reuse the connections in the Admin and Status objects to avoid leaking resources. Initialize the App and Admin objects themselves lazily at the first access. The Connection object has been changed to act as both an instance object and context manager. Change-Id: I4263b870a1099d345ab1940c61ccdf4680a706ca Closes-Bug: 1566946 (cherry picked from commit 728df1640f0db27fc541ad368341c98c1e77ef2c)
* | Updated from global requirementsOpenStack Proposal Bot2016-05-151-1/+1
|/ | | | Change-Id: I99ad5188dd6c5e39f0818c268658baeb8c787ae6
* Merge "Mysql GTID replication fails when data inserted" into stable/mitakaJenkins2016-05-124-0/+56
|\
| * Mysql GTID replication fails when data insertedDoug Shelley2016-05-064-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you have a master and a slave configured and you insert new data into the master, it will cause subsequent replica create to fail. The problem is that we weren't setting the gtid_purged variable using the metadata in the xtrabackup_binlog_info file. The Mysql GTID replication strategy was adjusted to account for this. A release note has been added. The replication scenario tests were enhanced to validate this issue. Note: this issue doesn't occur with MariaDB GTID replication because it mechanism is different. Scenario tests were run succesfully on Mysql, Percona and MariaDB with this change in place. Change-Id: I66c8b6278afa50ba14e4bb7888e3a25dc657a9e4 Closes-bug: 1563574 (cherry picked from commit 09a312ae3af1958df6dadcfd68dfae7261971fa3)
* | Merge "Notification exceptions not sent back correctly" into stable/mitakaJenkins2016-05-122-1/+5
|\ \
| * | Notification exceptions not sent back correctlyPeter Stachowski2016-05-092-1/+5
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | With the new notification feature added recently, exceptions that occur on the guest are sent back to the conductor. Due to a mis-match in the code however, the wrong call is being issued. The conductor api makes a call to notify_exception instead of notify_exc_info. This has been fixed. Change-Id: Ib2e04bb903c92b4d570913aba2e985db63c45096 Closes-Bug: #1577848 (cherry picked from commit 9f7be1a10b0a53c6d8bd783a714fac2864186600)
* | Merge "Do not remove root user on disable" into stable/mitakaJenkins2016-05-123-12/+12
|\ \
| * | Do not remove root user on disablePetr Malik2016-05-063-12/+12
| |/ | | | | | | | | | | | | | | | | | | | | The existence of the root user (with remote access) is used to determine whether root was ever enabled on a restored instance. Do not remove it, just generate a new random password for it. Change-Id: I8a4321ac062b1ec565945b49dbb7c619b6da867f Closes-Bug: 1549600 (cherry picked from commit 52bc1ab9c89cdca7c2556edb373ce3b59ace0295)
* | Merge "blacklist_regex is not an option" into stable/mitakaJenkins2016-05-121-1/+1
|\ \
| * | blacklist_regex is not an optionAttila Fazekas2016-05-061-1/+1
| |/ | | | | | | | | | | | | | | | | The devstack plugin uses blacklist_regex option which does not exists, instead of the existing black_list_regex option. Closes-Bug: 1570444 Change-Id: I0eaae3a17fb70c2294bec67b3778070e570df6f6 (cherry picked from commit 7fbe2dd8afe9b0c25feee17482711a0809bc19a5)
* | Merge "Enhance mongod pid find for multiple distros" into stable/mitakaJenkins2016-05-122-3/+2
|\ \
| * | Enhance mongod pid find for multiple distrosPeter MacKinnon2016-05-062-3/+2
| |/ | | | | | | | | | | | | | | | | Modify the FIND_PID system code use of ps to more specifically target the actual mongod or mongos process for different distros. Change-Id: Idbbaf8802396ff7c4f6c536b8c0e9a8169163c94 Closes-Bug: #1570866 (cherry picked from commit b9a06d968f191f8511ac4ba25506c3c1ccc85cdc)
* | Pass optional timeout to service commandsPetr Malik2016-05-063-18/+33
|/ | | | | | | | | | | | | | | | | | | | | Service commands may take some time to return. The current code does not pass any timeout value into the execute function resulting in the default 30s value being used. That value turns out to be too short for certain datastores (Cassandra) on slower/heavily-loaded systems. Trove already has a timeout (default=3min) for instance state changes that should be used instead (this timeout has already been used when polling for database states). The service command execute function have been updated to accept an optional timeout kwargs (like the shell command execute function). The state change timeout is now being passed in from DB start/stop/restart calls. Change-Id: I1ef45b95d9238a52a26f630961657755216786cb Closes-Bug: 1556314 (cherry picked from commit 87658dc4cc59f7c87d5631fbd6132b98384d396c)
* Updated from global requirementsOpenStack Proposal Bot2016-04-291-3/+3
| | | | Change-Id: I431bad31ea3b9868bb4c448b2ba40d3cbf88c84c
* Fixed kwargs being defaulted to CONF valuesBrandon Irizarry2016-04-184-6/+9
| | | | | | | | | | | The Trove code is full of numerous cases where kwargs are defaulted to CONF values. This is an error-prone way of setting up a default value, as python sets these one time only. This fix accounts for that. Change-Id: Icc0858ccb2d3e2584bf6f3d1542a7d631b251ac8 Closes-Bug: 1571076 (cherry picked from commit 64a869dbaf6ee583d667b4a6fd5fbbcd8902a646)
* Fixes migrations for MySQL 5.6.* and MariaDB 10.1.*Victoria Martinez de la Cruz2016-04-052-3/+35
| | | | | | | | | | | | | | | | | | | In MySQL 5.6/MariaDB 10.1 and later versions there was a change on the restrictions over foreign keys (FK). In 019-datastore-fix.py, we attempt to change a column that is part of a FK from NULL to not NULL. This sort of modifications are not longer allowed. This situation caused trove-manage db_sync and trove-manage db_migrate to fail. To workaround this, the FK check before executing the ALTER query is disabled and then reenabled. Change-Id: I666d01235f2c3225aca3fe7520ebdf6d53831cab Closes-Bug: #1473226 (cherry picked from commit 679e2283ecc888bd567955b4bf431c87043e8d12)
* Merge "Trove's tox tests should respect upper-constraints.txt" into ↵5.0.0.0rc25.0.0Jenkins2016-03-301-1/+25
|\ | | | | | | stable/mitaka
| * Trove's tox tests should respect upper-constraints.txtAmrith Kumar2016-03-301-1/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will force pip install to use the upper-constraints.txt specified version of pip modules. When you don't do this, you are out on the bleeding edge and become unstable everytime some python library in the wide world changes in a way that you don't expect. The releasenotes job has no constraints file, so override the install command there. This commit is being proposed on stable/mitaka and therefore the install command includes the clear designation of the branch. This is because, on branches other than master, we need to be sure to get the upper-constraints.txt file for that branch. Change-Id: I8417e0fefae9711d0f71b8f97bbb0e4ea5f8ccf2 Closes-Bug: #1563038 (cherry picked from commit aca90168f52169afb36500d6af77723b1a707008)
* | Address change in Route v2.3Amrith Kumar2016-03-301-2/+3
|/ | | | | | | | | | | | | | | | | | Routes v2.3 which just came out included a change (see the LP bug referenced below) that caused py27 to fail. At issue is that Routes<2.3 allowed both submapper.connect(route_name, route_path), and submapper.connect(route_path). In 2.3, you were required to provide both route_name and route_path. This change adds a route_name to support both Routes < 2.3 and Routes == 2.3. Change-Id: I8aa0626960fbf446102452a56369d24420422dac Related-Bug: 1563028 (cherry picked from commit 6664fb27af2218c411230f91b8e23e72845cbf2a)
* Update .gitreview for stable/mitakaThierry Carrez2016-03-181-0/+1
| | | | Change-Id: I5b43aab59d6cdbb9b24a7b5694c1f9f55fc7c259
* Merge "MongoDB cluster grow failing in get_admin_password"5.0.0.0rc1Jenkins2016-03-182-48/+23
|\
| * MongoDB cluster grow failing in get_admin_passwordMatt Van Dijk2016-01-082-48/+23
| | | | | | | | | | | | | | | | Fix the logic of creating/getting the admin password for MongoDB query routers. Change-Id: I9187a8db2e4e66bc8e0e61b4105fcef80d5ae705 Closes-bug: #1526024
* | Merge "Secure mongodb instances and clusters by default"Jenkins2016-03-183-26/+41
|\ \
| * | Secure mongodb instances and clusters by defaultMatt Van Dijk2016-03-173-26/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MongoDB's default behaviour is to have the authorization rules disabled. This means any client can access the database without credentials. This is too large of a risk for default behaviour, so authorization needs to be enabled by default. This fix addresses the problem by setting the authorization parameter to enabled for standalone instances, and specifying key files for cluster instances to use. Change-Id: I5895ce66ec450c3efce7a7e0f126ac13ac4c1b12 Closes-bug: #1507841
* | | Merge "Implementation of couchdb user and database functions"Jenkins2016-03-188-8/+838
|\ \ \
| * | | Implementation of couchdb user and database functionsIshita Mandhan2016-03-178-8/+838
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch implements the following functions and associated unit tests for the couchdb datastore- -create user -list user -delete user -get user -create database -list database -delete database -grant access -revoke access -list access -enable root -is root enabled Change-Id: I47759b5c1462c6f76b4631e4a915a3c3902dae1a Implements: blueprint couchdb-database-user-functions
* | | | Merge "Fix pagination function"Jenkins2016-03-184-12/+44
|\ \ \ \ | |/ / /
| * | | Fix pagination functionPetr Malik2016-03-174-12/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The marker should be the last element in the current page and not the first element in the next page. Also updated the scenario tests to account for different marker format of MySQL-based instances and fixed the assertion arg order. Change-Id: Iff5d9c4e55f9146ce7132c7968087b7e834e793e Closes-Bug: 1540172
* | | | Merge "updating the release notes from mitaka commits"Jenkins2016-03-1828-0/+232
|\ \ \ \
| * | | | updating the release notes from mitaka commitsCraig Vyvial2016-03-1728-0/+232
| | |/ / | |/| | | | | | | | | | | | | | | | | | Change-Id: I360c32c686161cf7bdd8afa1971a06c9ae2aa664 Author: Craig Vyvial <cp16net@gmail.com> Co-Authored-By: Amrith Kumar <amrith@tesora.com>
* | | | Merge "Add better validation to cluster shrink"Jenkins2016-03-184-20/+37
|\ \ \ \
| * | | | Add better validation to cluster shrinkMatt Van Dijk2016-03-164-20/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most cluster strategies need to block certain cluster shrink operations under some conditions. For example Vertica can easily determine if a master node has been targetted and should gracefully block this and notify the operator. Change-Id: I2fea16cd7eeec81510563daffcea1d2dbdf1eab5 Closes-bug: #1557784
* | | | | Fix incorrect innobackupex args (fixed gate)Peter Stachowski2016-03-172-10/+19
| |_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A recent release of Percona XtraBackup has tightened up the validation of options passed to the innobackupex script. See: https://www.percona.com/doc/percona-xtrabackup/2.3/release-notes/2.3/2.3.4.html https://bugs.launchpad.net/percona-xtrabackup/+bug/1533542 The options supplied to innobackupex in the MySQL restore strategy are slightly incorrect - this was ignored previously but now causes the backups to fail. The options are now specified correctly. Change-Id: Ic4671998f0c4467f17caa60cbb3106f49c505a2e Closes-Bug: #1558794
* | | | Merge "Redis should perform backup using BGSAVE not SAVE"Jenkins2016-03-163-33/+59
|\ \ \ \
| * | | | Redis should perform backup using BGSAVE not SAVEPeter Stachowski2016-02-013-33/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When Redis backup was implemented, using the save() command was chosen as it blocks, making the code simpler to read and understand. Unfortunately SAVE and BGSAVE have differences beyond one being synchronous and the other asynchronous, in that SAVE also blocks client connections while it runs. This behaviour is not optimal, so the code was changed to use BGSAVE and wait until it completes. In the case where bgsave() fails (possibly due to memory issues, save() is called so that the backup will still complete. The Redis helper was also modified to allow adding more data (to increase the time the backup takes) and tests were rearranged to improve chances of success. Change-Id: I75d9df54b8550b08ce0112e516c17fd717ebb857 Closes-Bug: #1538334
* | | | | Merge "Vertica configuration groups"Jenkins2016-03-1611-122/+1765
|\ \ \ \ \
| * | | | | Vertica configuration groupsAlex Tomic2016-03-1511-122/+1765
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Single instance configuration groups for vertica. Adds new Helper class to scenario int tests to allow generic config groups tests to be run against vertica. Change-Id: I0bf52032394ca65aabd082cf7be869b6441f04d9 Implements: bp/vertica-config-groups
View Lorry Controller Status