Bug 1548072 - DNS domain per network does not work
Summary: DNS domain per network does not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Assaf Muller
QA Contact: Federico Ressi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-22 16:11 UTC by Bernard Cafarelli
Modified: 2022-08-17 13:38 UTC (History)
10 users (show)

Fixed In Version: openstack-neutron-13.0.0-0.20180710125920.5db3979.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:48:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1774710 0 None None None 2018-06-01 19:34:03 UTC
OpenStack gerrit 516701 0 None None None 2018-06-01 20:17:35 UTC
OpenStack gerrit 571495 0 None None None 2018-08-22 17:39:36 UTC
OpenStack gerrit 571546 0 None None None 2018-06-01 19:34:19 UTC
OpenStack gerrit 571549 0 None None None 2018-06-04 12:46:45 UTC
Red Hat Issue Tracker OSP-4450 0 None None None 2022-08-17 13:38:24 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:49:22 UTC

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


Note You need to log in before you can comment on or make changes to this bug.