09a312ae3a
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
Trove
Trove is Database as a Service for OpenStack.
Usage for integration testing
If you'd like to start up a fake Trove API daemon for integration testing with your own tool, run:
$ ./tools/start-fake-mode.shStop the server with:
$ ./tools/stop-fake-mode.shTests
To run all tests and PEP8, run tox, like so:
$ toxTo run just the tests for Python 2.7, run:
$ tox -epy27To run just PEP8, run:
$ tox -epep8To generate a coverage report,run:
$ tox -ecover(note: on some boxes, the results may not be accurate unless you run it twice)
If you want to run only the tests in one file you can use testtools e.g.
$ python -m testtools.run trove.tests.unittests.python.module.path