Description of problem: # This is the similar problem as bz 1815512 , but for another component, so I'll file another independent one. In undercloud, we observe ironic-inspector always record logs into syslog, while it also record logs into its log files under /var/log/ironic-inspector . This is because we have the following configuration in inspector-dist.conf /etc/ironic-inspector/inspector-dist.conf ~~~ [DEFAULT] log_dir = /var/log/ironic-inspector state_path = /var/lib/ironic-inspector use_stderr = True <==========(*) ~~~ There are no reasons why ironic-inspector should record logs in deprecated locations, and this use_stderr should be false by default to be consistent with the other components like nova, neutron, and etc . /usr/share/nova/nova-dist.conf ~~~ [DEFAULT] log_dir = /var/log/nova state_path = /var/lib/nova lock_path = /var/lib/nova/tmp dhcpbridge = /usr/bin/nova-dhcpbridge dhcpbridge_flagfile = /usr/share/nova/nova-dist.conf dhcpbridge_flagfile = /etc/nova/nova.conf force_dhcp_release = True injected_network_template = /usr/share/nova/interfaces.template libvirt_nonblocking = True libvirt_inject_partition = -1 compute_driver = libvirt.LibvirtDriver rootwrap_config = /etc/nova/rootwrap.conf use_stderr = False <==========(*) ... ~~~ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy undercloud 2. See /var/log/messages in host Actual results: ironic-inspector logs are recorded in messages Expected results: ironic-inspector logs are not recorded in messages, but found only in ironic-inspector log files Additional info:
Verified in compose RHOS-16.1-RHEL-8-20200611.n.0. ()[ironic-inspector@hardprov-dl360-g9-01 /]$ cat /etc/ironic-inspector/inspector-dist.conf [DEFAULT] log_dir = /var/log/ironic-inspector state_path = /var/lib/ironic-inspector use_stderr = False There are no ironic-inspector logs in /var/log/messages.
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-2020:3148