Bug 1014606

Summary: error: rpmdbNextIterator: skipping h# 546 Header SHA1 digest: BAD
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Kortus <jkortus>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: jkortus, jzeleny, lkardos, pmatilai
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-15 13:13:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
corrupted RPM database none

Description Jaroslav Kortus 2013-10-02 11:40:13 UTC 
Description of problem:
Out of a sudden all rpm operations fail with this error message:
# rpm -q pacemaker
error: rpmdbNextIterator: skipping h#     546 Header SHA1 digest: BAD
[.. can repeat many times ...]

So far I was unable to find out what caused it. It happened two times to me so far (two different installations).

Version-Release number of selected component (if applicable):
# yum --version
3.2.29
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
  Installed: rpm-4.8.0-37.el6.x86_64 at 2013-09-19 12:08
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-09-12 10:55
  Committed: Panu Matilainen <pmatilai> at 2013-09-12

  Installed: subscription-manager-1.9.6-1.el6.x86_64 at 2013-09-19 12:10
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-09-12 20:11
  Committed: jesus m. rodriguez <jesusr> at 2013-09-12

  Installed: yum-3.2.29-40.el6.noarch at 2013-09-19 12:08
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2013-01-08 17:02
  Committed: James Antill <james.antill> at 2013-01-08


How reproducible:
not sure

Steps to Reproduce:
1. unknown
2.
3.

Actual results:
RPM commands start failing suddenly

Expected results:
no db corruption

Additional info:
Comment 1 Jaroslav Kortus 2013-10-02 11:43:34 UTC 
Created attachment 806395 [details]
corrupted RPM database
Comment 3 RHEL Program Management 2013-10-14 01:49:07 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 Ľuboš Kardoš 2014-11-25 11:04:49 UTC 
Attached rpmdb doesn't seem to be corrupeted. I extracted your tarball in rhel-6.5 system and successfully executed following command (where /root/rpm is path to extracted rpmdb):

# rpm --dbpath /root/rpm -q pacemaker
pacemaker-1.1.10-9.el6.x86_64

Also other commands worked as expected. Did you encounter this error right after installation? If yes then what kind of installation did you perform (default installation or some special steps)? If no then what steps did you perform in installed system before error occured?