Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1548072

Summary:	DNS domain per network does not work
Product:	Red Hat OpenStack	Reporter:	Bernard Cafarelli <bcafarel>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED ERRATA	QA Contact:	Federico Ressi <fressi>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	amuller, bcafarel, chrisw, fressi, jamsmith, nusiddiq, nyechiel, racedoro, ragiman, srevivo
Target Milestone:	Upstream M2	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-13.0.0-0.20180710125920.5db3979.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:48:58 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:

Description Bernard Cafarelli 2018-02-22 16:11:13 UTC

This feature is needed by the OpenShift on OpenStack group.

While the API already exists, it does not seem to work properly.

Comment 1 Assaf Muller 2018-06-01 20:17:35 UTC

Added external tracker link to CLI support - https://review.openstack.org/#/c/516701/. This is needed in addition to https://review.openstack.org/#/c/571546/, which fixes the issue in the DHCP agent.

Comment 2 Assaf Muller 2018-06-06 14:53:24 UTC

The bug fix was merged upstream. We still have the scenario test to iterate on.

Comment 6 Federico Ressi 2018-09-13 05:51:16 UTC

How can I reproduce this bug? Can you please provide some simple steps? Thanks

Comment 7 Bernard Cafarelli 2018-09-24 10:26:14 UTC

@Federico, going through the bug and patches, something like that should be good enough to confirm everything works:
* Create a network via openstack CLI with --dns-domain option
* check network has the option correctly set - this confirms CLI fix
* configure subnet, security groups for a VM test
* boot a VM with DHCP, check /etc/resolv.conf has the correct domain in it (not sure cirros dhcp client is enough, may need a fully fledged VM) - this confirms the DHCP agent side fix

Comment 14 errata-xmlrpc 2019-01-11 11:48:58 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/RHEA-2019:0045