Bug 1919272 - NM prepender script doesn't support systemd-resolved
Summary: NM prepender script doesn't support systemd-resolved
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Antonio Murdaca
QA Contact: Michael Nguyen
Depends On: 1919271
TreeView+ depends on / blocked
Reported: 2021-01-22 13:44 UTC by Vadim Rutkovsky
Modified: 2021-04-20 19:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1919271
Last Closed: 2021-04-20 19:27:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2356 0 None closed Bug 1919272: [release-4.6] NM resolve prepender: support appending a nameserver for systemd-resolved 2021-02-19 03:49:10 UTC
Red Hat Product Errata RHBA-2021:1153 0 None None None 2021-04-20 19:27:48 UTC

Description Vadim Rutkovsky 2021-01-22 13:44:04 UTC
+++ This bug was initially created as a clone of Bug #1919271 +++

Description of problem:
RHCOS is using NM to inject nameservers in resolv.conf, but FCOS is using systemd-resolved. In order to support OKD-on-FCOS the script should add a configuration dropin instead

Comment 21 errata-xmlrpc 2021-04-20 19:27:20 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 (OpenShift Container Platform 4.6.25 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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