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.
Bug 630983 - yum not working properly with yum-plugin-versionlock
Summary: yum not working properly with yum-plugin-versionlock
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On: 629274
Blocks: 592206
TreeView+ depends on / blocked
 
Reported: 2010-09-07 14:34 UTC by Karel Srot
Modified: 2014-01-21 06:19 UTC (History)
1 user (show)

Fixed In Version: yum-3.2.29-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: excludes of obsoleting packages didn't work properly Consequence: versionlock plugin couldn't lock over obsoletes properly Fix: add extra checks to make sure obsoleters exist Result: versionlock of obsoletes works again (and similar code)
Clone Of:
Environment:
Last Closed: 2011-05-19 13:33:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0602 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2011-05-19 09:37:29 UTC

Description Karel Srot 2010-09-07 14:34:18 UTC 
Description of problem:
I have created packages as described below. The point is to have
test-aaa-0.1-1 package installed and in the repo test-bbb-0.2-2 package that
obsoletes test-aaa. test-aaa-0.1-1 is also listed in
/etc/yum/pluginconf.d/versionlock.conf so it should not be updated.

After running "yum update" the package is not updated (that's fine) but I get
following output and yum exits with exit code 1:
...
Setting up Update Process
Error: Package tuple ('test-bbb', 'i386', '0', '0.2', '2') could not be found
in packagesack
[root@rhel6 rpm]#

If I disable versionlock in conf file the update is performed.

For more details see
https://bugzilla.redhat.com/show_bug.cgi?id=592206


Version-Release number of selected component (if applicable):
yum-3.2.27-13.el6.noarch
yum-utils-1.1.26-9.el6.noarch
yum-plugin-versionlock-1.1.26-11.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. have 4 packages like this:
   p = rpmfluff.SimpleRpmBuild('test-aaa', '0.1', '1')

   p = rpmfluff.SimpleRpmBuild('test-aaa', '0.2', '2')

   p = rpmfluff.SimpleRpmBuild('test-bbb', '0.1', '1')

   p = rpmfluff.SimpleRpmBuild('test-bbb', '0.2', '2')
   p.add_obsoletes('test-aaa')
2. # rpm -q test-aaa test-bbb
   test-aaa-0.1-1
   test-bbb-0.1-1
3. # cat /etc/yum/pluginconf.d/versionlock.conf'
[main]
enabled=1
locklist=/etc/yum/pluginconf.d/versionlock-bz449989.list
follow_obsoletes=1
   # cat /etc/yum/pluginconf.d/versionlock-bz449989.list
0:test-aaa-0.1-1.i386
4. # yum -y update  
Actual results:


Expected results:
no error message

Additional info:
Comment 1 Karel Srot 2010-09-08 07:07:21 UTC 
'yum check-update' is working
'yum update blah' and 'yum update' is not working

[root@rhel6-64 yum]# yum --disablerepo='*' --enablerepo=test update
Loaded plugins: refresh-packagekit, rhnplugin, versionlock
This system is not registered with RHN.
RHN support will be disabled.
Setting up Update Process
Error: Package tuple ('test-bbb', 'x86_64', '0', '0.1', '1') could not be found in packagesack
[root@rhel6-64 yum]# yum --disablerepo='*' --enablerepo=test update test-aaa
Loaded plugins: refresh-packagekit, rhnplugin, versionlock
This system is not registered with RHN.
RHN support will be disabled.
Setting up Update Process
Error: Package tuple ('test-bbb', 'x86_64', '0', '0.1', '1') could not be found in packagesack
[root@rhel6-64 yum]# yum --disablerepo='*' --enablerepo=test check-update
Loaded plugins: refresh-packagekit, rhnplugin, versionlock
This system is not registered with RHN.
RHN support will be disabled.
Comment 6 James Antill 2011-05-12 19:17:18 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: excludes of obsoleting packages didn't work properly 
Consequence: versionlock plugin couldn't lock over obsoletes properly
Fix: add extra checks to make sure obsoleters exist
Result: versionlock of obsoletes works again (and similar code)
Comment 7 errata-xmlrpc 2011-05-19 13:33:41 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0602.html
Note You need to log in before you can comment on or make changes to this bug.