Some of the tests expect to be able to sort on the pool NS record priority. However, the rand_ns_records fake data generator can create NS records with equal priority which leads to undefined sort orders and ultimately invalid test failures.[2]
This patch makes sure the fake ns records created for tests never have equal priority values.
[2] https://zuul.opendev.org/t/openstack/build/69325d93f36042f390b4301cfadd3aa8/log/job-output.txt#21738
Change-Id: Ic04d1fe093dee54da64ccb238e9650ad5fc47eb8
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.
Change-Id: I6ee56fcc1f00bc55012bcd1895bddce5acfa07d4
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
- https://review.opendev.org/c/openstack/releases/+/881254
Change-Id: I94f8511ab4adab2dfba21260c69c6e691911e16d
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[1]. With that we do not need to test the
stable/wallaby jobs on master gate
[1] https://review.opendev.org/c/openstack/devstack/+/871782
Change-Id: If5db25580fc979f9b4184e3556d2e1f1ed227c6f
This patch updates the tests to account for projects that have a zone
shared with it can list and show the zone.
Change-Id: I218bbf0c4f6a1609b6500ccb91765959823bf911
The 'all-plugin' tox environment was deprecated by this patch [1].
Instead of the 'all-plugin' it is recommended to use the 'all' tox
environment.
This patch removes any reference to 'all-plugin' tox environment and
updates the documentation so that the installation steps work with
the 'all' venv.
[1] https://review.opendev.org/c/openstack/tempest/+/543974
Change-Id: Id3451147d172002d67b4557680560a59b026ed77
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.
Change-Id: Icf18d59a8fdf67e1e9ee893954703a53b0b9f070
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.
Change-Id: I85d871350fcacfb6e293092ff6c16a6dba7f952e
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
Change-Id: I0bbc6504ba2ef75bba8268d5e91b2588a4215555
This patch updates the Designate tempest plugin to accommodate stable
branches that still have keystone scoped tokens. The "Direction
change"[1] means scoped tokens were dropped in the Bobcat (2023.2)
release. However the stable branches back to Wallaby will still have
scoped tokens available as a configuration option.
[1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#direction-change
Change-Id: Ia57b5126dbc9fbe98cbcaa7ad0e11d36c21a14da
This patch re-enables the tempest tests with the keystone default roles
job and adds the Antelope (2023.1) stable job.
Change-Id: Idaa3e0e90fb3f7d6b754d9b0814e945bda009650
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.
Change-Id: I8645fb7577d52cd35e3d61d44ca9028ea3afe00f
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.
Related-Bug: #1964509
Depends-On: https://review.opendev.org/c/openstack/tempest/+/871018
Change-Id: I143e69c1e150ddf7fa1757dea7bced6bff6739a9
This patch adds API and scenario test coverage for the shard zones
feature.
Author: Igor Malinovskiy <u.glide@gmail.com>
Co-Authored-By: Sergey Drozdov <sergey.drozdov.dev@gmail.com, sergey.drozdov93@thehutgroup.com>
Co-Authored-By: Michael Johnson <johnsomor@gmail.com>
Change-Id: I53a1e4676c5bbb63bee0c4bb91eac03c95dd3a3c
Partial-Bug: #1714088
Depends-On: https://review.opendev.org/726334
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.
Change-Id: I240911c0ab9b9bad7851268865d6a8e867627673
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.
Change-Id: I8f41bb8188ba8442dbf493dac39b8601f5208938
It's worth adding propagation check to this test:
'test_create_and_delete_records_on_existing_zone'
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.
Change-Id: I4796efc3deb79b5135f667f6880349b70aa016c7
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.
Change-Id: Ibcee798b15aaccf8fddd28f80df7112cda3a9ed5
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.
Closes-Bug: 1968717
Change-Id: I08ea6758994a9bbd95bf9693ce344c2206818241
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I20e9be1071c27301a07089ec70c9ceb53fca7633
This patch [1] 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
QueryClient.
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.
[1] https://review.opendev.org/c/openstack/designate-tempest-plugin/+/860116
Change-Id: Iedd151b2e47ed62adc168a97cb6021ccb47abb0f
After stable/zed was released, we should also test updates to the
tempest-plugin against that branch.
Change-Id: I877732fa51f60d2b50fb552a63e00df76f80b690
It will be inherited via the designate-devstack-jobs project template,
so we can drop the explicit setting.
Depends-On: https://review.opendev.org/c/openstack/designate/+/861352
Change-Id: Ib555ea19c183149ebdf25f7915089c405c23644d
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.
Change-Id: I156508e404dc2d2966a189941b0b4ff13412953f
Test scenario:
1) Create a tenant and set its Zones quota to 1
2) Create a first zone --> PASS
3) Create a second Zone --> FAIL (413 over_quota)
Change-Id: Ic47888d83a77b6f65213c1e55bbfca73eb5346b7
Zuul