Bug 1919271 - 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.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Vadim Rutkovsky
QA Contact: Michael Nguyen
Depends On:
Blocks: 1919272
TreeView+ depends on / blocked
Reported: 2021-01-22 13:43 UTC by Vadim Rutkovsky
Modified: 2021-02-24 15:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: NM prepender script supports systemd-resolved Reason: FCOS has switched to systemd-resolved to control /etc/resolv.conf and no longer uses networkmanager's copy of resolv.conf to set nameservers Result: NM prepender script correctly sets mDNS nameserver when /etc/resolv.conf is controlled by systemd-resolved
Clone Of:
: 1919272 (view as bug list)
Last Closed: 2021-02-24 15:55:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2359 0 None closed Bug 1919271: [on-prem] NM resolve prepender: support appending a nameserver for systemd-resolved 2021-02-08 18:34:55 UTC
Github openshift machine-config-operator pull 2377 0 None closed Bug 1919271: NM resolve prepender: Update for systemd-resolved logic. systemd-resolved requires restart after dropin cre... 2021-02-08 18:34:55 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:55:49 UTC

Description Vadim Rutkovsky 2021-01-22 13:43:01 UTC
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 6 errata-xmlrpc 2021-02-24 15:55:29 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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.