Bug 757072

Summary: Sesame update replace configuration file (sesame is then set to default configuration).
Product: Red Hat Enterprise MRG Reporter: Daniel Horák <dahorak>
Component: sesameAssignee: Trevor McKay <tmckay>
Status: CLOSED ERRATA QA Contact: Daniel Horák <dahorak>
Severity: high Docs Contact:
Priority: high    
Version: 1.0CC: iboverma, ltoscano, matt, sgraf
Target Milestone: 2.1   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: sesame-1.0-2 Doc Type: Bug Fix
Doc Text:
C: sesame.conf is marked as %config in the sesame RPM C: The file, even if user modified, is overwritten on upgrade. This causes users to re-modify the file to include broker host location. F: sesame.conf was changed to %config(noreplace) in the sesame RPM R: User modifications are maintained across upgrades.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-23 17:29:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 743350    

Description Daniel Horák 2011-11-25 12:29:22 UTC
Description of problem:
Sesame update replace configuration file with the new one (and backup the old one to /etc/sesame/sesame.conf.rpmsave), instead of preservation configured file and put the new one to sesame.confg.rpmnew.

Version-Release number of selected component (if applicable):
sesame-1.0-1

How reproducible:
100%

Steps to Reproduce:
1. Install sesame from stable version of MRG 2.0
2. Update to sesame from MRG 2.1
  
Actual results:
Old (and configured) file /etc/sesame/sesame.conf is backed-up as /etc/sesame/sesame.conf.rpmsave and is replaced with the new one. Then sesame is not configured. 
    Updating: sesame           9/18 
  warning: /etc/sesame/sesame.conf saved as /etc/sesame/sesame.conf.rpmsave

Expected results:
New configuration file don't replace current configuration and it is saved as /etc/sesame/sesame.conf.rpmnew and sesame is still configured also after update.

Comment 1 Matthew Farrellee 2011-11-28 20:45:06 UTC
This is a spec change, %config to %config(noreplace)

Having sesame.conf replaced means all configuration changes (broker host, "host") must be re-applied across the pool on each upgrade.

There is no meaningful change in sesame.conf content from last to 1.0.

Comment 3 Matthew Farrellee 2011-11-30 11:47:43 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:
C: sesame.conf is marked as %config in the sesame RPM
C: The file, even if user modified, is overwritten on upgrade. This causes users to re-modify the file to include broker host location.
F: sesame.conf was changed to %config(noreplace) in the sesame RPM
R: User modifications are maintained across upgrades.

Comment 5 Daniel Horák 2011-11-30 14:18:10 UTC
Verified on RHEL 5.7 i386, x86_64 and RHEL 6.2 i386, x86_64.

Old configured file sesame.conf is now observed and the new one is created as sesame.conf.rpmnew.

    Updating       : sesame                             
  warning: /etc/sesame/sesame.conf created as /etc/sesame/sesame.conf.rpmnew

>>> VERIFIED

Comment 6 errata-xmlrpc 2012-01-23 17:29:46 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/RHEA-2012-0045.html