Bug 2077776

Summary: [OSP16.1] subnet with 0.0.0.0 creates an entry in resolv.conf
Product: Red Hat OpenStack Reporter: ggrimaux
Component: python-networking-ovnAssignee: Miguel Lavalle <mlavalle>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: apevec, averdagu, lhh, majopela, ralonsoh, scohen
Target Milestone: z9Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-7.3.1-1.20220922083226.4e24f4c.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-07 20:26:21 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: 2077775, 2126110    
Bug Blocks:    

Description ggrimaux 2022-04-22 08:38:32 UTC
Description of problem:
If a subnet is created with a dns-nameserver of 0.0.0.0, instances have a dns entry "nameserver 0.0.0.0".
It seems to not be what our doc says should happen.

I think we need to backport this fix:
https://review.opendev.org/c/openstack/neutron/+/822297

Thank you!

Version-Release number of selected component (if applicable):
OSP16.1

How reproducible:
100%

Steps to Reproduce:
1. Set subnet with 0.0.0.0 nameserver
2. Reboot an instance in this subnet
3. resolv.conf in the instance has an entry "nameserver 0.0.0.0"

Actual results:
resolv.conf has an entry with "nameserver 0.0.0.0"

Expected results:
No entry at all

Additional info:
None.

Comment 9 errata-xmlrpc 2022-12-07 20:26:21 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 (Red Hat OpenStack Platform 16.1.9 bug fix and enhancement 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-2022:8795