Bug 1795165

Summary:	test_internal_dns.InternalDNSTest.test_dns_domain_and_name fails with OVN
Product:	Red Hat OpenStack	Reporter:	Jakub Libosvar <jlibosva>
Component:	python-networking-ovn	Assignee:	Maciej Józefczyk <mjozefcz>
Status:	CLOSED ERRATA	QA Contact:	Eran Kuris <ekuris>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	16.0 (Train)	CC:	amcleod, apevec, bcafarel, ccopello, chrisw, dalvarez, ekuris, gregraka, jamsmith, jlibosva, jschluet, lhh, majopela, mjozefcz, rhos-maint, rsafrono, scohen
Target Milestone:	z1	Keywords:	AutomationBlocker, Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-7.1.0-0.20200115181916.949b7f8.el8ost	Doc Type:	Known Issue
Doc Text:	There is a known issue for OpenStack Networking (neutron) where all instances created inherit the dns_domain value associated with the network, and not the dns_domain value configured for an internal DNS. The cause of this issue is that the network dns_domain attribute overrides the neutron dns_domain config option. To avoid this issue, do not set the dns_domain attribute for the network if you want to use the internal DNS feature.	Story Points:	---
Clone Of:	1718211	Environment:
Last Closed:	2020-03-03 09:41:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 10 Eran Kuris 2020-02-12 15:06:53 UTC

https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/networking-ovn/job/DFG-network-networking-ovn-16_director-rhel-virthost-3cont_2comp-ipv4-geneve/131/testReport/neutron_tempest_plugin.scenario.test_internal_dns/InternalDNSTest/

According CI run  the bug fixed and verified
core_puddle: RHOS_TRUNK-16.0-RHEL-8-20200212.n.0
python3-networking-ovn-7.1.0-0.20200204065607.57ac389.el8ost.noarch.rpm

Comment 12 errata-xmlrpc 2020-03-03 09:41:29 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:0654