Bug 1871139

Summary: [systemd] systemd-resolved.service:33: Unknown lvalue 'ProtectSystems' in section 'Service'
Product: Red Hat Enterprise Linux 8 Reporter: Frank Liang <xiliang>
Component: systemdAssignee: David Tardon <dtardon>
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: high Docs Contact:
Priority: high    
Version: 8.3CC: dtardon, jamacku, jlyle, leiwang, linl, mark, o.freyermuth, peter.vreman, ribarry, rmetrich, sbroz, systemd-maint-list, thomas.juberg, vkuznets, wienemann, ymao
Target Milestone: rcKeywords: ZStream
Target Release: 8.3   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-239-43.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1934500 (view as bug list) Environment:
Last Closed: 2021-05-18 14:53:56 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: 1934500    

Description Frank Liang 2020-08-21 12:14:02 UTC 
systemd-resolved.service has a typo in 'Service' section. "ProtectSystems" should be "ProtectSystem".

The error in journal log:
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: Detected architecture x86-64.
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: Set hostname to <ip-10-22-1-46.us-west-2.compute.internal>.
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: /usr/lib/systemd/system/systemd-resolved.service:33: Unknown lvalue 'ProtectSystems' in section 'Service'
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: systemd-journald.service: Succeeded.
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: initrd-switch-root.service: Succeeded.
Aug 21 11:25:54 ip-10-22-1-46.us-west-2.compute.internal systemd[1]: Stopped Switch Root.
# cat systemd-resolved.service
"""
[Service]
Type=notify
Restart=always
RestartSec=0
ExecStart=!!/usr/lib/systemd/systemd-resolved
WatchdogSec=3min
User=systemd-resolve
CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE
PrivateTmp=yes
PrivateDevices=yes
ProtectSystems=strict <- typo
ProtectHome=yes
"""
# rpm -qf /usr/lib/systemd/system/systemd-resolved.service
systemd-239-36.el8.x86_64
Version-Release number of selected components (if applicable):

RHEL Version:
RHEL-8.3(4.18.0-221.el8.x86_64)

How reproducible:
100%

Steps to Reproduce:
1. Start a RHEL8.3  instance
2. Enable systemd-resolved.service and reboot system
3. Check journal log.

Actual results:
'ProtectSystems' is not acceptable.

Expected results:
No such error in journal log

Additional info:
- N/A
Comment 2 David Tardon 2020-11-06 08:52:59 UTC 
*** Bug 1895278 has been marked as a duplicate of this bug. ***
Comment 3 Lukáš Nykrýn 2020-11-24 17:21:50 UTC 
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/133
Comment 7 David Tardon 2020-12-09 08:26:54 UTC 
*** Bug 1905742 has been marked as a duplicate of this bug. ***
Comment 13 errata-xmlrpc 2021-05-18 14:53:56 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: systemd 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-2021:1611