Bug 767037

Summary:	/etc/rsyslog.conf is not persistent
Product:	Red Hat Enterprise Linux 6	Reporter:	Guohua Ouyang <gouyang>
Component:	ovirt-node	Assignee:	Joey Boggs <jboggs>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3	CC:	acathrow, bsarathy, cshao, jboggs, leiwang, mburns, moli, ovirt-maint, sgordon, thildred, ycui
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-node-2.2.1-1.el6	Doc Type:	Bug Fix
Doc Text:	Previously, the configuration file for rsyslog was not persisted by default. This caused any changes to the configuration to be lost on hypervisor reboot. Now the rsyslog configuration file is persisted by default, and any configuration changes are persisted across reboots.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-19 14:16:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Guohua Ouyang 2011-12-13 03:04:09 UTC

Description of problem:
/etc/rsyslog.conf is not persistent after configure it in logging.


Version-Release number of selected component (if applicable):
6.2-20111209.1

How reproducible:
100%.

Steps to Reproduce:
1. configure rsyslog server in logging.
2. Do some actions and checking the log is saved to remote server.
3. Drop to shell, check whether /etc/rsyslog.conf is persisted, $(grep rsyslog /config/files)  return none.
4. Reboot, check the TUI, no rsyslog server address displayed there.

Actual results:
/etc/rsyslog.conf is not persistent.

Expected results:
/etc/rsyslog.conf should be persisted. 

Additional info:
It's also happened on 6.2-20111117.0 build.

Comment 6 Mike Burns 2012-01-12 23:51:46 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The rsyslog configuration is lost after reboot.  This is caused by not persisting the rsyslog.conf file.  The file is now persisted

Comment 7 Tim Hildred 2012-01-25 01:42:23 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1,3 @@
-The rsyslog configuration is lost after reboot.  This is caused by not persisting the rsyslog.conf file.  The file is now persisted+Previously, the configuration file for rsyslog was not persisted by default. This caused any changes to the configuration to be lost on hypervisor reboot. 
+
+Now the rsylog configuration file is persisted by default, and any configuration changes are persistent across reboots.

Comment 9 Stephen Gordon 2012-03-27 20:10:05 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1,3 @@
 Previously, the configuration file for rsyslog was not persisted by default. This caused any changes to the configuration to be lost on hypervisor reboot. 
 
-Now the rsylog configuration file is persisted by default, and any configuration changes are persistent across reboots.+Now the rsyslog configuration file is persisted by default, and any configuration changes are persistent across reboots.

Comment 10 Stephen Gordon 2012-05-28 16:22:55 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,3 +1,3 @@
 Previously, the configuration file for rsyslog was not persisted by default. This caused any changes to the configuration to be lost on hypervisor reboot. 
 
-Now the rsyslog configuration file is persisted by default, and any configuration changes are persistent across reboots.+Now the rsyslog configuration file is persisted by default, and any configuration changes are persisted across reboots.

Comment 12 errata-xmlrpc 2012-07-19 14:16:48 UTC

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.

http://rhn.redhat.com/errata/RHBA-2012-0741.html