Bug 124514

Summary: rpm verify misses "missing files/links"
Product: [Fedora] Fedora Reporter: John Floyd <john.floyd>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-29 12:53: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:

Description John Floyd 2004-05-27 04:14:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
My Problem:
Somehow lost links in rc0.d files for S* scripts. Which caused locked
up shutdown.  Had a sector remap on disk! probably due to power
outage.  Left me with a number of missing directories and files.

The real Fedora Problem:
Doing a verify via rpm did not pick this up even though these are
listed in file list with rpm -qi.  Eventually found problem by
investigation.

This may be problem iwith rpm and not initscripts.

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

How reproducible:
Always

Steps to Reproduce:
1.remove links to S* in rc0.d
2.run rpm -V initscripts
3.
    

Actual Results:  rpm -v shows no problems.

Expected Results:  rpm should show missing files/links

Additional info:

Comment 1 Jeff Johnson 2004-05-29 12:53:08 UTC
The scripts in rc0.d may or may not exist depending on
how the machine is configured, and hence are marked
    %config(missingok)
in the package (i.e. it is not a verify failure if
the file is not found).


Comment 2 John Floyd 2004-05-30 22:18:16 UTC
Yes I can understand this argument - but also isnt the verify there to
indicate differences to what was initially installed.  Other
components of verify show changed permissions on file etc which are
also dependent on "how the machine is configured" for use. 

Also, in this case a major script was missing ie the link back to the
halt script - shouldnt this stay regardless.