Bug 235627

Summary:	up2date clobbers modified files
Product:	Red Hat Enterprise Linux 4	Reporter:	monty <monty>
Component:	up2date	Assignee:	Bret McMillan <bretm>
Status:	CLOSED NOTABUG	QA Contact:	Brandon Perkins <bperkins>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-22 15:02:45 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 monty 2007-04-08 15:19:35 UTC

Description of problem:
When up2date installed the recent update to mysql (RHSA-2007:0152-01) it replaced the file /etc/
init.d/mysqld even though the file had been modified before running up2date. This change to the file 
broke the MySQL installation on the server.

up2date did not create a backup of the file before it was replaced.
up2date did not send any notification.
up2date did not log the change.

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


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Red Hat Bugzilla 2007-04-12 02:20:09 UTC

User bnackash's account has been closed

Comment 2 Todd Sanders 2007-05-22 15:02:45 UTC

This is not a bug with up2date.  rpm -Uhv would exhibit the same behavior.  Only
config files are persisted through an rpm upgrade. Please log this error against
mysql, if you feel that packaging needs modification.