Bug 1905742

Summary:	Systemd-resolved misses ProtectSystem=strict in service file
Product:	Red Hat Enterprise Linux 8	Reporter:	Oliver Freyermuth <o.freyermuth>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	dtardon, systemd-maint-list, wienemann
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-09 08:26: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:

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 ***