RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1871139 - [systemd] systemd-resolved.service:33: Unknown lvalue 'ProtectSystems' in section 'Service'
Summary: [systemd] systemd-resolved.service:33: Unknown lvalue 'ProtectSystems' in sec...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.3
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
: 1895278 1905742 (view as bug list)
Depends On:
Blocks: 1934500
TreeView+ depends on / blocked
 
Reported: 2020-08-21 12:14 UTC by Frank Liang
Modified: 2021-08-27 22:41 UTC (History)
16 users (show)

Fixed In Version: systemd-239-43.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1934500 (view as bug list)
Environment:
Last Closed: 2021-05-18 14:53:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd-rhel rhel-8 pull 133 0 None closed (#1871139) fix typo in ProtectSystem= option 2020-12-09 08:27:24 UTC

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


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