Bug 1550191

Summary:	'After=network.target' missing in rsyslog-8.24.0-12 default unit file
Product:	Red Hat Enterprise Linux 7	Reporter:	Juan Manuel Santos <jsantos>
Component:	rsyslog	Assignee:	Radovan Sroka <rsroka>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	kwalker, sdordevi
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
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:	2018-03-01 08:24:49 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 Juan Manuel Santos 2018-02-28 18:13:47 UTC

Description of problem:
rsyslog-7.4.7-16 (RHEL 7.3) introduced a patch (https://bugzilla.redhat.com/show_bug.cgi?id=1263853) to insert an 'After=network.target' line in the default systemd unit file under /usr/lib/systemd/system/rsyslog.service. This change is no longer present on rsyslog-8.24.0-12.el7.x86_64 (RHEL 7.4)

Version-Release number of selected component (if applicable):
rsyslog-8.24.0-12.el7.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Install RHEL (rsyslog-8.24 is provided by default on RHEL 7.4)
2. Verify rsyslog does not start before network.target
3. Verify /usr/lib/systemd/system/rsyslog.service does not contain 'After=network.target'

Actual results:
/usr/lib/systemd/system/rsyslog.service does not contain 'After=network.target' and rsyslog can start before the network.target


Expected results:
/usr/lib/systemd/system/rsyslog.service should contain 'After=network.target' so rsyslog is only started after reaching network.target


Additional info:
This patch could have been omitted due to the 8.24 rebase.