Bug 678644
Summary: | yum reinstall hangs | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | awilliam, ffesti, jnovy, pmatilai, robatino |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | RejectedBlocker | ||
Fixed In Version: | rpm-4.9.0-0.rc1.3.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-03-03 03:03:01 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: |
Description
Orion Poplawski
2011-02-18 17:50:02 UTC
Downgrading to rpm-4.9.0-0.beta1.7.fc15.1.x86_64 did not appear to help. Yes, I did a clean install from TC2 x86_64 last night, installed fedora-release*-15-0.7 from Koji, then updated, then after trying to reinstall fedora-release*-15-0.7, it hung. I don't have the VM any more, though. Just did a text-based install from the x86_64 TC2 DVD, brought up the network, did "yum reinstall fedora-release", and it hung. I'm seeing this as well on rawhide. rpm-4.9.0-0.rc1.1.fc16.x86_64 yum-3.2.29-4.fc15.noarch I can reproduce it in the same way on i386, so you can change the Platform to "All Linux". (And due to comment 4, you could change the Version to "rawhide".) I can't reproduce with rpm -Uvh --force libsemanage-2.0.46-3.fc15.x86_64.rpm. Not sure what yum is doing that would be different. Discussed at 2011-02-18 blocker review meeting. Rejected as blocker, does not hit Alpha criteria: updating does not require --reinstall to work. Using "rpm -Uvh --replacepkgs fedora-release-15-0.7.noarch.rpm" works for me. Trying to use yum shell with an erase and install command as a substitute for yum reinstall works if the package is getting updated (so there are two separate transactions) but not if the package is already updated (so it says it is reinstalling and only does one transaction). Never mind, erase followed by install would be more or less equivalent to an update when the package changes. I think that in general using rpm might require both the --replacefiles and --replacepkgs options (but not --oldpackage). Right, I can easily reproduce this. It appears to deadlock on rpmdb access, and be related to yum using two different handles to the rpmdb (making it use just one fixes the hang). It doesn't happen with rpm 4.8.x though... so while yum is at least in part guilty here, I need to check what causes the difference between 4.8 and 4.9 here. Fixed in rpm-4.9.0-0.rc1.3 (fc15/16). Yum is indeed being a bit naughty, but there was a real rpm bug (regression) involved, good thing it was caught. rpm-4.9.0-0.rc1.3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/rpm-4.9.0-0.rc1.3.fc15 rpm-4.9.0-0.rc1.3.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rpm'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/rpm-4.9.0-0.rc1.3.fc15 rpm-4.9.0-0.rc1.3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |