Bug 1766467

Summary:	Designate service is not automatically detected in discover-tempest-config
Product:	Red Hat OpenStack	Reporter:	Takashi Kajinami <tkajinam>
Component:	python-tempestconf	Assignee:	Chandan Kumar <chkumar>
Status:	CLOSED ERRATA	QA Contact:	Martin Kopec <mkopec>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	chkumar, udesale
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tempestconf-2.4.0-1.el7ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-10 11:52:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1785177, 1795976
Bug Blocks:

Description Takashi Kajinami 2019-10-29 07:34:48 UTC

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:

Comment 3 Martin Kopec 2020-02-19 22:28:14 UTC

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.

Comment 6 errata-xmlrpc 2020-03-10 11:52:51 UTC

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