https://github.com/openshift/openshift-ansible/pull/11193
Verify this bug with openshift-ansible-3.9.70-1.git.0.d5a98de.el7 By default, journald.conf would be updated by openshift-ansible as below: [root@qe-gpei-392master-etcd-1 ~]# cat /etc/systemd/journald.conf # Managed by OpenShift Ansible # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See journald.conf(5) for details. [Journal] Storage=persistent Compress=True #Seal=yes #SplitMode=uid SyncIntervalSec=1s RateLimitInterval=1s RateLimitBurst=10000 SystemMaxUse=8G SystemKeepFree=20% SystemMaxFileSize=10M #RuntimeMaxUse= #RuntimeKeepFree= #RuntimeMaxFileSize= MaxRetentionSec=1month MaxFileSec=1day ForwardToSyslog=False #ForwardToKMsg=no #ForwardToConsole=no ForwardToWall=False #TTYPath=/dev/console #MaxLevelStore=debug #MaxLevelSyslog=debug #MaxLevelKMsg=notice #MaxLevelConsole=info #MaxLevelWall=emerg #LineMax=48K With journald_vars_to_replace=[] set in ansible inventory file, update journald conf step would be skipped: TASK [openshift_node : Update journald setup] ********************************** Thursday 28 February 2019 11:40:36 +0800 (0:00:00.361) 0:09:50.558 ***** TASK [openshift_node : Tag journald managed by Ansible] ************************ Thursday 28 February 2019 11:40:36 +0800 (0:00:00.037) 0:09:50.595 ***** skipping: [ec2-54-162-115-187.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0403