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 1905742 - Systemd-resolved misses ProtectSystem=strict in service file
Summary: Systemd-resolved misses ProtectSystem=strict in service file
Keywords:
Status: CLOSED DUPLICATE of bug 1871139
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-08 23:37 UTC by Oliver Freyermuth
Modified: 2020-12-09 08:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-09 08:26: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 68 0 None closed (#1810869) resolved: Recover missing PrivateTmp=yes and ProtectSystem=struct 2020-12-08 23:37:32 UTC

Description Oliver Freyermuth 2020-12-08 23:37:32 UTC 
Description of problem:
System logs contain:
systemd[1]: /usr/lib/systemd/system/systemd-resolved.service:33: Unknown lvalue 'ProtectSystems' in section 'Service'
after starting systemd-resolved. 
Also, "ProtectSystem=strict" is not part of the service file. 

Version-Release number of selected component (if applicable):
systemd-239-41.el8_3.x86_64

How reproducible:
Always

Steps to Reproduce:
1. systemctl start systemd-resolved
2. Watch logs with journalctl. 

Actual results:
Warning in the log as outlined, ProtectSystem=strict not set. 

Expected results:
No warning, ProtectSystem=strict being set. 

Additional info:
The typo was introduced via:
https://github.com/systemd-rhel/rhel-8/pull/68
which tried to resolve bz#1810869 but did that only partially. .
Comment 1 David Tardon 2020-12-09 08:26:56 UTC 

*** This bug has been marked as a duplicate of bug 1871139 ***
Note You need to log in before you can comment on or make changes to this bug.