Bug 1241067

Summary: [abrt] yum-cron: rpmsack.py:93:_get_hdr:PackageSackError: Rpmdb changed underneath us
Product: [Fedora] Fedora Reporter: Thom Carlin <tcarlin>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: admiller, jsilhan, packaging-team-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4b8100746daa0421369e12dda8d67e70c7812453
Whiteboard: abrt_hash:60f5bf3004c863303c75ad94617146a2ebafceb1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 15:15:24 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:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Thom Carlin 2015-07-08 11:45:18 UTC
Version-Release number of selected component:
yum-cron-3.4.3-505.fc22

Additional info:
reporter:       libreport-2.6.0
cmdline:        /usr/bin/python -tt /usr/sbin/yum-cron /etc/yum/yum-cron-hourly.conf
dso_list:       yum-3.4.3-505.fc22.noarch
executable:     /usr/sbin/yum-cron
kernel:         4.0.5-300.fc22.x86_64
runlevel:       N 5
type:           Python
uid:            0

Truncated backtrace:
rpmsack.py:93:_get_hdr:PackageSackError: Rpmdb changed underneath us

Traceback (most recent call last):
  File "/usr/sbin/yum-cron", line 713, in <module>
    main()
  File "/usr/sbin/yum-cron", line 710, in main
    base.updatesCheck()
  File "/usr/sbin/yum-cron", line 616, in updatesCheck
    self.findDeps()
  File "/usr/sbin/yum-cron", line 503, in findDeps
    (res, resmsg) = self.buildTransaction()
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1214, in buildTransaction
    (rescode, restring) = self.resolveDeps()
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 915, in resolveDeps
    for po, dep in self._checkFileRequires():
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 1206, in _checkFileRequires
    self.installedFileProviders = self.rpmdb.fileRequiresData()
  File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 970, in fileRequiresData
    for name, flag, evr in pkg.requires:
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 678, in <lambda>
    requires = property(fget=lambda self: self.returnPrco('requires'))
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1435, in returnPrco
    self._populatePrco()
  File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1474, in _populatePrco
    hdr = self._get_hdr()
  File "/usr/lib/python2.7/site-packages/yum/rpmsack.py", line 93, in _get_hdr
    raise Errors.PackageSackError, 'Rpmdb changed underneath us'
PackageSackError: Rpmdb changed underneath us

Local variables in innermost frame:
self: <RPMInstalledPackage : file-libs-5.22-3.fc22.x86_64 (0x7f06cb18b2d0)>
mi: <rpm.mi object at 0x7f06c8524ad0>
ts: <rpmUtils.transaction.TransactionWrapper instance at 0x7f06cae9dcb0>

Potential duplicate: bug 1040033

Comment 1 Thom Carlin 2015-07-08 11:45:20 UTC
Created attachment 1049828 [details]
File: backtrace

Comment 2 Thom Carlin 2015-07-08 11:45:21 UTC
Created attachment 1049829 [details]
File: environ

Comment 3 Fedora End Of Life 2016-07-19 15:15:24 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.