The current code assumes that the nameserver value configured
in tempest.conf is one of these two options only: IPV4 or IPV4:PORT
There is no handling for IPV6 addresses(with/without PORT).
(If IPV6 is set it causes traceback).
This patch adds support for IPV6.
stable/xena is in EM state. As Tempest and
plugins masters does not support EM stable branches
QA team will be pinning tempest in devstack stable/xena
soon. With that we do not need to test the stable/xena
jobs on master gate
stable/wallaby is in EM state. As Tempest and
plugins masters does not support Em stable branches
qa team is pinning tempest in devstack stable/wallaby
tesitng. With that we do not need to test the
stable/wallaby jobs on master gate
The 'all-plugin' tox environment was deprecated by this patch .
Instead of the 'all-plugin' it is recommended to use the 'all' tox
This patch removes any reference to 'all-plugin' tox environment and
updates the documentation so that the installation steps work with
the 'all' venv.
Scoped tokens do not have a project_id, which caused some of the new
shared zones tests to fail. This patch corrects that issue by using sudo
project ids if scoped tokens is enabled for the test.
This patch unrolls the test_update_records_propagated_to_backends tests from
DDT to ensure each test gets a proper idempotent ID. Previously fourteen tests
had the same ID.
This patch also fixes a scenario where if no nameservers are provided in the
tempest.conf, the test would pass instead of being skipped.
This patch adds:
1) API and Scenario test cases for Admin tenant
2) Quota tests, to ensure: "quotas enforced against owner"
3) Negative scenario tests
This patch updates the README file to have instructions for running the tempest tests using the "all" environment instead of "all-plugins". The "all-plugins" environment has been deprecated for years and uses site-packages, which may cause unintended test scenarios.
It also updates the example "run a single test" to be a non-admin API test.
Tempest is fixing the bug#1964509 (depends-on) where
project_reader user will be created under the same project
as primary, project_member, project_admin users.
'primary', 'project_admin', 'project_member', and 'project_reader'
creds will be created in same projects. All the alt creds will be
created under the new projects. non alt and alt creds will use
different project, for example, 'project_alt_member' and
'project_member' creds will be created in different project.
This patch adds API and scenario test coverage for the shard zones
Author: Igor Malinovskiy <email@example.com>
Co-Authored-By: Sergey Drozdov <firstname.lastname@example.org, email@example.com>
Co-Authored-By: Michael Johnson <firstname.lastname@example.org>
This patch adds a method that allows us to get the current Designate API version under test for use in test classes to skip tests against new features introduced in a specific API version.
This patch also centralizes the "primary" zones client to be instantiated once and updates the tests to use a standardized name for the client.
Finally, it adds a missing requirement of oslo.serialization to requirements.txt.
This patch adds the Designate hacking checks to also run against
the Designate tempest plugin code to maintain consistent style
checking across the Designate repositories.
It's worth adding propagation check to this test:
This (DDT based) test covers almost all supported record types
and therefore it makes sense using a query client here
to ensure successfully create/delete of the recordset on the backends
for each tested type.
The test_list_enabled_api_versions was not properly checking the enabled API versions and would always fail on new API version additions.
This patch corrects the list comprehension and updates the test to look for at least one of the base API versions in the returned results. This way the test will not artificially fail as we add new API versions.
This patch removes the test_manually_trigger_update_secondary_zone_negative test because it is broken due to changes in dnspython and the need for this negative test is not clear.
This patch  introduced checking whether the CONF.dns.nameservers
is empty. If the CONF.dns.nameservers value is empty then the
initialization of the QueryClient fails. This change makes the majority
of designate-tempest-plugin tests fail even tests that do not use the
This patch introduces three changes:
1) ValueError is raised only when the query() function is called so
that only tests that actually use the query() function fail.
2) wait_for_query() function is fixed so that it never succeeds when the
CONF.dns.nameservers value is empty.
3) Skip tests that rely upon [dns].nameserver value.
There is no sense to "dig" not existing DNS backends, therefor
when Query Client object is being created with an empty list for
the namesrevers attribute, ValueError will be raised.