Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
AssertionError and python traceback seem to occur when installing an RPM if all 3 of the following conditions are met:
1) The RPM being installed is listed in "installonlypkgs" in /etc/yum.conf
2) The RPM being installed obsoletes a currently installed package
3) The RPM being installed contains a %post scriptlet
I first hit this scenario while attempting to perform a "yum upgrade" to install a newer customized kernel that obsoletes "cpuspeed", which was installed.
I've reproduced this issue with test packages which I'll call "package-A" and "package-B", and /etc/yum.conf lists "package-A" in installonlypkgs.
Package-A version 1.0 is installed
Package-B version 1.0 is installed
Package-A version 2.0 obsoletes Package-B.
When attempting to yum install Package-A version 2.0, I get the traceback listed below under "Actual results:".
Version-Release number of selected component (if applicable):
yum-3.2.29-69.el6.centos.noarch
How reproducible:
Always reproducible
Steps to Reproduce:
1. Install package-A (version 1.0) and package-B (version 1.0)
2. Modify /etc/yum.conf to add package-A to installonlypkgs
3. Attempt to install package-A (version 2.0)
Actual results:
[root@localhost x86_64]# yum install package-A-2.0-1.x86_64.rpm
Loaded plugins: fastestmirror, security
Setting up Install Process
Examining package-A-2.0-1.x86_64.rpm: package-A-2.0-1.x86_64
Marking package-A-2.0-1.x86_64.rpm as an update to package-A-1.0-1.x86_64
Loading mirror speeds from cached hostfile
* base: mirrors.psychz.net
* epel: linux.mirrors.es.net
* extras: dallas.tx.mirror.xygenhosting.com
* updates: mirror.hostduplex.com
Resolving Dependencies
--> Running transaction check
---> Package package-A.x86_64 0:2.0-1 will be obsoleting
---> Package package-A.x86_64 0:2.0-1 will be installed
---> Package package-B.x86_64 0:1.0-1 will be obsoleted
--> Finished Dependency Resolution
Dependencies Resolved
=====================================================================================================================
Package Arch Version Repository Size
=====================================================================================================================
Installing:
package-A x86_64 2.0-1 /package-A-2.0-1.x86_64 0.0
replacing package-B.x86_64 1.0-1
package-A x86_64 2.0-1 /package-A-2.0-1.x86_64 0.0
replacing package-B.x86_64 1.0-1
Transaction Summary
=====================================================================================================================
Install 2 Package(s)
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
Installing : package-A-2.0-1.x86_64 1/1
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 470, in callback
self._scriptStop(bytes, total, h);
File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 636, in _scriptStop
name, txmbr = self._getTxmbr(h)
File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 331, in _getTxmbr
assert len(txmbrs) == 1
AssertionError
error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0xc14c68>> failed, aborting!
[root@localhost x86_64]#
Expected results:
Package-B is removed
Additional info:
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: AssertionError and python traceback seem to occur when installing an RPM if all 3 of the following conditions are met: 1) The RPM being installed is listed in "installonlypkgs" in /etc/yum.conf 2) The RPM being installed obsoletes a currently installed package 3) The RPM being installed contains a %post scriptlet I first hit this scenario while attempting to perform a "yum upgrade" to install a newer customized kernel that obsoletes "cpuspeed", which was installed. I've reproduced this issue with test packages which I'll call "package-A" and "package-B", and /etc/yum.conf lists "package-A" in installonlypkgs. Package-A version 1.0 is installed Package-B version 1.0 is installed Package-A version 2.0 obsoletes Package-B. When attempting to yum install Package-A version 2.0, I get the traceback listed below under "Actual results:". Version-Release number of selected component (if applicable): yum-3.2.29-69.el6.centos.noarch How reproducible: Always reproducible Steps to Reproduce: 1. Install package-A (version 1.0) and package-B (version 1.0) 2. Modify /etc/yum.conf to add package-A to installonlypkgs 3. Attempt to install package-A (version 2.0) Actual results: [root@localhost x86_64]# yum install package-A-2.0-1.x86_64.rpm Loaded plugins: fastestmirror, security Setting up Install Process Examining package-A-2.0-1.x86_64.rpm: package-A-2.0-1.x86_64 Marking package-A-2.0-1.x86_64.rpm as an update to package-A-1.0-1.x86_64 Loading mirror speeds from cached hostfile * base: mirrors.psychz.net * epel: linux.mirrors.es.net * extras: dallas.tx.mirror.xygenhosting.com * updates: mirror.hostduplex.com Resolving Dependencies --> Running transaction check ---> Package package-A.x86_64 0:2.0-1 will be obsoleting ---> Package package-A.x86_64 0:2.0-1 will be installed ---> Package package-B.x86_64 0:1.0-1 will be obsoleted --> Finished Dependency Resolution Dependencies Resolved ===================================================================================================================== Package Arch Version Repository Size ===================================================================================================================== Installing: package-A x86_64 2.0-1 /package-A-2.0-1.x86_64 0.0 replacing package-B.x86_64 1.0-1 package-A x86_64 2.0-1 /package-A-2.0-1.x86_64 0.0 replacing package-B.x86_64 1.0-1 Transaction Summary ===================================================================================================================== Install 2 Package(s) Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum. Installing : package-A-2.0-1.x86_64 1/1 Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 470, in callback self._scriptStop(bytes, total, h); File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 636, in _scriptStop name, txmbr = self._getTxmbr(h) File "/usr/lib/python2.6/site-packages/yum/rpmtrans.py", line 331, in _getTxmbr assert len(txmbrs) == 1 AssertionError error: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0xc14c68>> failed, aborting! [root@localhost x86_64]# Expected results: Package-B is removed Additional info: