Bug 1919271

Summary: NM prepender script doesn't support systemd-resolved
Product: OpenShift Container Platform Reporter: Vadim Rutkovsky <vrutkovs>
Component: Machine Config OperatorAssignee: Vadim Rutkovsky <vrutkovs>
Status: CLOSED ERRATA QA Contact: Michael Nguyen <mnguyen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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
Story Points: ---
Clone Of:
: 1919272 (view as bug list) Environment:
Last Closed: 2021-02-24 15:55:29 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:    
Bug Blocks: 1919272    

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.

https://access.redhat.com/errata/RHSA-2020:5633