RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 767037 - /etc/rsyslog.conf is not persistent
Summary: /etc/rsyslog.conf is not persistent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 03:04 UTC by Guohua Ouyang
Modified: 2016-04-26 15:33 UTC (History)
11 users (show)

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.
Clone Of:
Environment:
Last Closed: 2012-07-19 14:16:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0741 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2012-07-19 18:10:46 UTC

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
Note You need to log in before you can comment on or make changes to this bug.