Designate tests if failing on scenario003 job

Bug #2016592 reported by Arx Cruz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Won't Fix
Critical
Unassigned

Bug Description

Log:

https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-scenario003-standalone-master/3358cd5/logs/undercloud/var/log/tempest/stestr_results.html.gz

Error:

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/designate_tempest_plugin/tests/api/v2/test_recordset.py", line 551, in test_delete_zone_with_existing_recordset
    record = self.client.create_recordset(
  File "/usr/lib/python3.9/site-packages/designate_tempest_plugin/services/dns/json/base.py", line 39, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/designate_tempest_plugin/services/dns/v2/json/recordset_client.py", line 62, in create_recordset
    waiters.wait_for_recordset_status(
  File "/usr/lib/python3.9/site-packages/designate_tempest_plugin/common/waiters.py", line 210, in wait_for_recordset_status
    raise lib_exc.TimeoutException(message)
tempest.lib.exceptions.TimeoutException: Request timed out
Details: (RecordsetsTest:test_delete_zone_with_existing_recordset) Recordset 5732931e-715d-442c-9239-24a3333a6809 failed to reach status=ACTIVE within the required time (360 s). Current status: PENDING

This is is constantly failing, and it started after https://opendev.org/openstack/designate/commit/964562cc65ccf5619fe53c7b60898edec3b0605b get merged, so I believe it is a real issue.

Ronelle Landy (rlandy)
Changed in tripleo:
milestone: none → antelope-1
Revision history for this message
Michael Johnson (johnsom) wrote :

That patch is unrelated (it only effected secondary zones which none of these tests use). These tests have never passed on a tripleo installed deployment because the name server list (from tripleo) is not being configured in the tempest.conf file.

If you look at the tempest.conf for the test run:
[dns]
nameservers = 1.1.1.1

Which is incorrect, it should be configured with the tripleo deployed BIND instance IP addresses. This will cause all of the tests that update zone records or query the backend DNS servers to fail.

Please reference the following BZ for this issue: 2116862 – Designate DNS – OOO setup, missing DNS nameservers in tempest.conf

Link to tempest.conf from the test run: https://logserver.rdoproject.org/openstack-periodic-integration-main/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-9-scenario003-standalone-master/3358cd5/logs/undercloud/home/zuul/tempest/etc/tempest.conf.txt.gz

Revision history for this message
Arx Cruz (arxcruz) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-quickstart-extras (master)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Arx Cruz (arxcruz) wrote :

Closing as we are no longer supporting the master branch

Changed in tripleo:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.