Description of problem: Currently discover-tempest-config doesn't care about designate service, and we don have service_available/designate set in tempest.conf . Current integration guide says that we can install openstack-tempest-all packages to install all tempest plugins. However, if we install this, we see that tempest runs designate tests, which is enabled by default, and have many failed tests. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/openstack_integration_test_suite_guide/chap-install-tempest#sec-install-tempest-packages How reproducible: Always Steps to Reproduce: 1. Deploy overcloud without Designate 2. Run smoke test following "OpenStack Integration Test Suite Guide", with installing openstack-tempest-all Actual results: Tempest shows failure in designate tests Expected results: Tempest does not run designate tests Additional info:
The problem is fixed in python-tempestconf version 2.4.0, python-tempestconf is able to designate service in that version. The BZ which tracked import of the new version downstream got VERIFIED so this BZ can be VERIFIED as well.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0769