| Summary: | error during update | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | george monroe <geomonroe> |
| Component: | PackageKit | Assignee: | Richard Hughes <rhughes> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0 | CC: | tcallawa, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-06 11:26:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
new to linux, sorry in advance for bug reporting ignorance. dont hesitate to contact me if i can be of more assistance! Hi George. Did you ever reproduce this? Would it be possible that an rpm transaction was running at the same time as the updates check was going on? For instance, manually upgrading or removing a package on the command line with "rpm -e foo-package"? Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |
Description of problem: File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 2025, in _update_packages txmbr = self.yumbase.update(po=pkg) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 3370, in update updated_pkg = self.getInstalledPackageObject(updated) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 2612, in getInstalledPackageObject raise Errors.RpmDBError, _('Package tuple $s could not be found in rpmdb') $ str(pkgtup) RpmDBError: Package tuple ('kernel-firmware', 'noarch', '0', '2.6.32', '71.18.1.el6') could not be found in rpmdb Version-Release number of selected component (if applicable): GNOME 2.28.2 KERNAL LINUX 2.6.32-71.18.1.el6.x86_64 How reproducible:reran software update. said all software is up to date. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: