Description of problem: The configuration for rsyslog server through TUI is not saved in /etc/rsyslog.conf file. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20151009.0.iso ovirt-node-3.3.0-0.13.20151008git03eefb5.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H with network enabled. 2. Configure rsyslog server as 10.66.1.1 in TUI. 3. Check the /etc/rsyslog.conf file. Actual results: 1. After step3, no infos about rsyslog server was added to /etc/rsyslog.conf file. Expected results: 1. It should add as "*.* @@10.66.1.1:514" to /etc/rsyslog.conf file. Additional info:
Reverting that patch will cause regressions in multiple other bugs. Rsyslog does not work at all on EL7 without it. I'm looking at the old patch, because I'm positive it got tested. There was a change at patch set 8 (after the last time I verified it) which moved all of the augeas logic to ovirt.node.utils.system, but it uses the same class name (Syslog) as ovirt.node.config.defaults, but this change was not reflected in config.defaults. It looks like the intention was to use utils.system.Rsyslog, but the class naming didn't reflect that, and rebasing the patch 9 months later missed the difference. It's a one-line fix to use the actual logic, but note that "*.* @@some.host:514" will not work, since there were not (last time I checked) augeas lenses for tcp hosts (or ipv6 hosts), but udp will work fine, and that's the default configuration.
The patch looks reasonable. And keeping the patch open for 9 months - was just not the right way to handle it. Merged it because it's an easy and low risk patch.
Test version: rhev-hypervisor-7-7.2-20151104.0.e17ev ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch Test step: 1. Install RHEV-H with network enabled. 2. Configure rsyslog server as 10.66.1.1 in TUI. 3. Check the /etc/rsyslog.conf file. Test result: 1. Configuration is added in /etc/rsyslog.conf. ### end of the forwarding rule ### *.* @10.66.1.1:514 So this bug is fixed in ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch.
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://rhn.redhat.com/errata/RHBA-2016-0378.html