Bug 178063

Summary:	netdump should use %config(noreplace) for /etc/sysconfig/netdump
Product:	Red Hat Enterprise Linux 4	Reporter:	Linda Wang <lwang>
Component:	netdump	Assignee:	Dave Anderson <anderson>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2006-0038	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-03-07 18:26:08 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:
Bug Depends On:
Bug Blocks:	168429

Description Linda Wang 2006-01-17 17:25:13 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4

Description of problem:
The netdump config file is a sample, and changes are required to get netdump to work.  But when the config is modified and noReplaceConfig is enabled for up2date, it will not be updated.

When noReplaceConfig is enabled, netdump should still be allowed to update and the config file should not be overwritten (much like the behavior of up2date itself).  This equates to building the netdump package with %config(noreplace) in the spec file.

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

How reproducible:
Always

Steps to Reproduce:
1.load up RHEL4 distro
2.cause kernel panic
3.take a netdump
  

Actual Results:  When noReplaceConfig is enabled, netdump didn't allowed to update and the config file got overwritten

Expected Results:  When noReplaceConfig is enabled, netdump should still be allowed to update and the config file should not be overwritten.

Additional info:

Comment 5 Red Hat Bugzilla 2006-03-07 18:26:08 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0038.html