Bug 2155745 - A DNS server is added to an instance even though the subnet's dns servers field is empty
Summary: A DNS server is added to an instance even though the subnet's dns servers fie...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-22 08:02 UTC by Itzik Brown
Modified: 2022-12-22 08:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-21008 0 None None None 2022-12-22 08:07:28 UTC

Description Itzik Brown 2022-12-22 08:02:22 UTC 
Description of problem:
A server has two networks.
One of the networks has a subnet with empty dns_nameservers field.

When looking into the instance's /etc/resolv.conf a nameserver from the Controller's /etc/resolv.conf is added

Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20221206.n.1

How reproducible:
100%

Steps to Reproduce:
As mentioned in the description

Actual results:
A DNS server is added even when the subnet has empty dns_nameservers field.

Expected results:
No DNS server will be added when a subnet has empty dns_nameservers field.


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