Bug 2077776 - [OSP16.1] subnet with 0.0.0.0 creates an entry in resolv.conf
Summary: [OSP16.1] subnet with 0.0.0.0 creates an entry in resolv.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z9
: 16.1 (Train on RHEL 8.2)
Assignee: Miguel Lavalle
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 2077775 2126110
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-22 08:38 UTC by ggrimaux
Modified: 2022-12-07 20:26 UTC (History)
6 users (show)

Fixed In Version: python-networking-ovn-7.3.1-1.20220922083226.4e24f4c.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-07 20:26:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-14833 0 None None None 2022-04-22 08:44:56 UTC
Red Hat Product Errata RHBA-2022:8795 0 None None None 2022-12-07 20:26:48 UTC

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


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