Bug 1507202

Summary:	rsyslog-8.24.0-12.el7.x86_64 starts before network.target during boot
Product:	Red Hat Enterprise Linux 7	Reporter:	Amey <abetkike>
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:	sdordevi
Target Milestone:	rc
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:	2017-10-30 09:31:50 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 Amey 2017-10-28 08:43:08 UTC

Description of problem:
In RHEL 7.4 rsyslog-8.24.0-12.el7.x86_64 starts before network.target during boot, so if rsyslog is configured to send logs to remote server on boot it will log locally however remote login will not work and as a workaround you need to manually restart the rsyslog service

Version-Release number of selected component (if applicable):

RHEL 7.4, rsyslog-8.24.0-12.el7.x86_64 

How reproducible:
always


Steps to Reproduce:
1. edit rsyslog.conf to send logs to central rsyslog server.
2. on central rsyslog server make changes to accept TCP traffic
3. take reboot of client system
4. you will notice rsyslog logs locally however it fails to log to central log server.

rsyslog starts befor network.target this can be verified using below-
# systemd-analyze critical-chain rsyslog.service
## systemd-analyze plot > plot.svg     

Actual results:

rsyslog logs locally but not to central syslog server after boot

Expected results:

rsyslog should log locally as well as to central syslog server after boot


Additional info:

Comment 2 Radovan Sroka 2017-10-30 09:31:50 UTC

Closing as duplicate of rhbz#1401456.

*** This bug has been marked as a duplicate of bug 1401456 ***