Bug 1574860

Summary:	Changing the journald.conf when installing or upgrading to OCP3.7
Product:	OpenShift Container Platform	Reporter:	Andre Costa <andcosta>
Component:	RFE	Assignee:	Brenton Leanhardt <bleanhar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.1	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-18 15:00:34 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 Andre Costa 2018-05-04 08:05:17 UTC

Description of problem:
When installing or upgrading OCP 3.7 there's a role playbook which configures the /etc/systemd/journald.conf and restarts the systemd-journald.service. Changing the SystemMaxUse=8G causes the filesystem usage to increase and this may cause the atomic-openshift services to stop. 

Version-Release number of selected component (if applicable):
Openshift v3.7

How reproducible:
This seems to be hard-coded on the playbooks used by the installer

Expected results:
Customer would like to have the possibility to have variables to use on the inventory hosts file in order to setup the journald.conf
Without any option the solution now is to manually configure this file on OCP nodes.

Additional info:
https://github.com/openshift/openshift-ansible/issues/6465

Comment 3 Scott Dodson 2019-04-18 15:00:34 UTC

We cleaned up the ability to configure journald options in the follow bugs for 3.11 and 3.10.

https://bugzilla.redhat.com/show_bug.cgi?id=1667185
https://bugzilla.redhat.com/show_bug.cgi?id=1676905