they are not maintained for a long time, and trove already switch
the tests to templest.
This commit removes the usage of them. more details see story.
Story: 2010882
Task: 48606
Depends-On: https://review.opendev.org/c/openstack/trove/+/914228
Change-Id: Ie021e0bd708cf8ed13853dea632312af38190205
- 'HEALTHY' means the db service is responsive, 'ACTIVE' means the db
service is alive.
- Remove the CI job fakemodetests, but will add similar testing task in
the future.
- Fix the periodic CI job
- Remove MongoDB and related jobs
Change-Id: I5abe9091ba203297dc87db5fba139179166321f7
Functional tests are executed by trovestack script, which uses python
in default OS version which is 2.7.
This change wraps python in tox and executes trovestack int_tests in
virtual enviroment, starting them in python3.
Any future python version change could be managed by tox framework.
Change-Id: I3a849978241d3d0669ef9e1c802ff504ac3c32cb
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I9ee34642c700d1e6ba9c2f3891b7fa1f7f7e1e1d
Depends-On: I8989fd4798e80eae27408017e1543819a68b4ab1
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
Co-Authored-By: Doug Hellmann <doug@doughellmann.com>
Replace basestring with six.string_types and add a hacking rule
to check it. This modification refers to neutron and merge
translation_checks into checks .Follow-up will modify the other
on the python3 common
Change-Id: I66d58ecaf664705660bbeb85058ad3cd092ef82f
reference:https://github.com/openstack/neutron/tree/master/neutron/hacking
As an aid to debug guest failures, a Metaclass was added
to the TestRunner class that allows failed tests to
pull back and echo the guest log from 'registered'
instances.
This uses the guest-log feature that is available for
all datastores.
IDs for instances created in the tests were registered
to report on failures.
Two guest-log tests were also commented out, as they
seem to not work properly: see
https://bugs.launchpad.net/trove/+bug/1653614
This was discovered while testing the new retrieval
code. Other tests were also modified so that
'SkipTest' exceptions would be raised properly.
Change-Id: I448bd2f0181351ef1536e20c41f9d45f95478587
Partial-Bug: 1652964
If a node is really slow then a single test can take longer than an
hour. It will then fail as the client it has cached will now have an
expired token. To alleviate this, the caching of the clients was removed
(since the time saved on caching the clients is probably negligible
anyway).
Checking the client code was also cleaned up for a number of tests.
The cluster tests were modified, however the code was reverted as
there is no way to test it at present (they will not run as they
haven't been modified to work with the new neutron set up). This
will be fixed in a separate changereq (since they are currently not
being tested in the gate, this should not hold up development).
Change-Id: I63d5b78084486b806bff38068260e42128c0d0ed
Closes-Bug: 1647002
This change uses the alt-demo network instead of sharing
the private network from the demo tenant. This should
fix the tempest tests on python-troveclient complaining
about this and also brings us one step closer to using
neutron entirely.
Tested with the demo tenant as well and it still
puts on a network without using the --nic parameter, the
only drawback is that the ip doesn't appear on the trove
show command.
The scenario and api tests were modified to always pass
in the nic parameter (as it probably should have been done
from the beginning anyways).
Change-Id: I9f3cbae3490e9995ba5f835fc2304442b83464e4
Closes-Bug: 1647001
In the SQLAlchemy keep_alive class, MariaDB is failing
as pymysql reports an invalid packet sequence.
MariaDB seems to timeout the client in a different
way than MySQL and PXC, which manifests itself as the
aforementioned invalid sequence. It is now handled
as a special-case exception.
With this fix, the MariaDB scenario tests now pass.
The scenario tests were also tweaked a bit, which aided
in the testing of the fix. 'group=instance' was created,
plus instance_error properly interleaved with
instance_create. _has_status now calls get_instance with
the admin client so that any faults are accompanied by
a relevant stack trace. Cases where the result code
was being checked out-of-sequence were removed, and explicit
calls to check the http code for the right client were added.
The replication error messages for promote and eject were
enhanced as well to attempt to debug spurious failures.
One of those failures was 'Replication is not on after 60 seconds.'
This was fixed by setting 'MASTER_CONNECT_RETRY' in the mariadb
gtid replication strategy as was done in:
https://review.openstack.org/#/c/188933
Finally, backup_incremental was added to MariaDB supported
groups and cleaned up elsewhere.
Closes-Bug: #1621702
Change-Id: Id6bde5a34e1d79eece3084f761dcd153c38ccbad
Slow query time should be configurable on per-instance basis
via the existing configuration group mechanism (see the bug).
We need to deprecate the existing global conf property first.
The property has been deprecated on all datastores.
Validation rules have been updated on those that
support log retrieval as well:
- MySQL: long_query_time
- Percona: long_query_time
- Percona XtraDB Cluster: long_query_time
- PostgreSQL: log_min_duration_statement
- MariaDB: long_query_time
The logging settings will be saved with lower 'priority' than
any user settings. This will ensure the user settings
(if present) always override the global value.
Once the deprecated options go away we can again apply
the logging settings at the system level.
Change-Id: I9c28ceb933b6819b8e96556584b2e26cab2155fb
DocImpact: Document deprecated properties
Partial-Bug: 1542485
This changeset stitches together all the different groups
in a way to have 3 instances being created at any given
time (where possible). The groupings will be:
-- module
|- configuration
-- instance_actions
-- database_actions
|- backup
-- instance_actions
-- user_actions
|- root_actions
-- guest_log
-- replication
Times (on a fast test machine) went from 2230s to 1720s, an
improvement of 23%.
The group labels were moved into the __init__.py file to facilitate
being accessed by different group implementations (to avoid a
circular import issue).
Tests were also cleaned up and homogenized wherever possible.
Change-Id: Idc3daab243261584ac5fa9350d952f5bb3984300
Closes-Bug: #1571092
The configuration group scenario tests were broken into separate
parts to facilitate parallel runs in the gate.
Change-Id: Id6f4b0a4060d6c88e547b62e74f97df881cf4425
Partial-Bug: #1571092
The scenario tests need to have the group classes broken
up to allow interleaving of the different parts of the tests
so that the gate can finish in a reasonable amount of time.
The runners, however, need to be the same for each main group,
thus allowing state to be preserved between groups of the same
feature. The creation of runners was refactored to allow for this.
The module tests were also modified to use the new paradym, which
allowed the removal of the global varaibles in the runner.
Dependencies on tests.api were also removed.
Change-Id: I66fcb2bce8c6cbc99c9ff071c242e4741500056d
Partial-Bug: #1571092
Add 'datastore' and 'datastore_version' to the
'create_instance_with_conf' test.
Change-Id: Id448a494600a3033cc06ebbb45cd13d68e233262
Closes-Bug: 1566412
Datastore agnostic support was added for configuration
groups in the int-tests. The new groups was added to
the supported int-tests for Cassandra, Redis and MongoDB.
(plus MySQL, of course.)
The tests can be run by:
./redstack int-tests --group=configuration
(or --group=<datastore>_supported)
Co-Authored-By: Petr Malik <pmalik@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
Change-Id: Ib265165b145f32bf0c911f43ed205f82d4e5f97d