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 677410 - Download sig check now holds the rpmdb ts lock, for all of downloads
Summary: Download sig check now holds the rpmdb ts lock, for all of downloads
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-14 17:11 UTC by James Antill
Modified: 2014-01-21 06:20 UTC (History)
3 users (show)

Fixed In Version: yum-3.2.29-6.el6
Doc Type: Bug Fix
Doc Text:
Certain commits caused yum to hold the RPM database open throughout the remaining package download, after the first signature check happened. As a consequence, when a user pressed Ctrl+C, the shortcut could not be properly recognized and reacted upon. With this update, this bug has been fixed and no longer occurs.
Clone Of:
Environment:
Last Closed: 2011-05-19 13:34:08 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 James Antill 2011-02-14 17:11:19 UTC 
Description of problem:

See:

http://lists.baseurl.org/pipermail/yum-devel/2011-February/007898.html

...we now hold a ts across downloads, simple fix for 6.1 is to just undo that commit ... it's much less useful on RHEL-6 than Fedora. But importing the upstream fix is also viable.

 I've marked this as a regression, but truthfully I have no idea how well C-c works without this bug ... so it might not really be a regression from RHEL-6.0, so could wait until 6.2 etc.
Comment 2 Karel Srot 2011-03-28 08:36:47 UTC 
James, 
I can see the patch is applied in yum-3.2.29-4.el6 but I can't see any strange behavior after Ctrl-C during pkg download. Did I miss something?
Comment 3 James Antill 2011-03-28 16:06:53 UTC 
 You mean you can't see any weird behaviour with C-c before -4 ? That's pretty special, but then that's rpm for you :)
 Did you check with a normal repo. or an RHN repo?

 Given the fix in BZ-677410-Download-sig-check-holds-the-rpmdb-ts-lock.patch ... it's pretty risk free, and anything with that patch should behave as the 6.0 yum does. But confirmation that it breaks, and is fixed is always nice :).
Comment 4 Karel Srot 2011-03-29 06:31:37 UTC 
Well, in yum..-4 I can see the commit applied. As I understand, This commit is causing holding rpmdb open during the download and thus Ctrl-C during the download may result in "some" issue... And bz677410 is removing that commit.
Therefore I was checking it on -4 to see what is that issue so I can verify it does not occur in later versions.

I was using normal repo. After "yum update" I have pressed Ctrl-C during the download of the second package (is that right?). But as I said, didn't saw anything strange. Maybe my test scenario is not correct.
Comment 7 Tomas Capek 2011-05-17 12:00:29 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:
Certain commits caused yum to hold the RPM database open throughout the remaining package download, after the first signature check happened. As a consequence, when a user      pressed Ctrl+C, the shortcut could not be properly recognized and reacted upon. With this update, this bug has been fixed and no longer occurs.
Comment 8 errata-xmlrpc 2011-05-19 13:34:08 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.