Description of problem: Rsyslog doesn't work when using server's hostname as server address. Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.0-3.999.999.20130716190656git4e57356.2850.fc18.iso ovirt-node-3.0.0-3.999.20130716190656git4e57356.fc18.noarch How reproducible: 100% Steps to Reproduce: 1. Clear install ovirt-node. 2. Configure network and change the dns server into 10.66.11.225 to resolve the hostname we set next. 3. Ping the server with its hostname. 4. Using hostname as rsyslog server address. Rsyslog is an enhanced multi-threaded syslogd Server Address: example Server Port: 514 5. Check in remote rsyslog server. # nc -l -u 514 In local host, run # echo "test" > /dev/kmsg Actual results: After step3, the server is reachable. After step5, Rsyslog doesn't work. Expected results: After step5, Rsyslog works well. Additional info: 1.No such issue when set Netconsole server address as the same hostname as we set in Rsyslog server. 2.When set rsyslog server with ip address(10.66.106.88), it can receive some messages from rhevh6.5, but also can not recevice the message using # echo "test" > /dev/kmsg command.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
how is this an interesting use case in real life of deploying the node as the syslog server?
IIUC, this is about using a hostname instead of an IP address in rsyslog.conf rather than using Node as a syslog server This isn't reproducable on current EL6 images, but is on EL7, as rsyslog.conf is missing a directive to load the module for journald
Itamar, see comment 5.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Test version: rhev-hypervisor7-7.2-20160126.0 ovirt-node-3.6.1-5.0.el7ev.noarch Test steps: 1. Clean install rhev-hypervisor7-7.2-20160126.0. 2. Configure network and change the dns serverto resolve the hostname we set next. 3. Ping the server with its hostname. 4. Using hostname as rsyslog server address. Rsyslog is an enhanced multi-threaded syslogd Server Address: example Server Port: 514 5. Check in remote rsyslog server. # nc -l -u 514 In local host, run # echo "test" > /dev/kmsg Test result: 1. After step5, Rsyslog works well. So this issue is fixed in ovirt-node-3.6.1-5.0.el7ev.noarch. Change the status to verified.