Bug 448430
Summary: | Yum throwing an AttributeError: CHECKSUM_VALUE on update | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Vincent Castellano <surye80> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | CC: | ddumas, griffint, jhutar, richard.johnson, sfolkwil, tao |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-07 13:57:36 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
Vincent Castellano
2008-05-26 19:15:32 UTC
> After an update, I can no longer perform a yum update or yum install.
What update did you do?
Does a simple "yum update" get to the "y/N" prompt?
Does "yum clean all" help?
Does "yum update yum" work?
Also what does: yum list yum\* ...display? > What update did you do? Whole system, was about 300 packages. > Does a simple "yum update" get to the "y/N" prompt? No, same output at above. > Does "yum clean all" help? Nope > Does "yum update yum" work? Nope, same error. > yum list yum\* [2008-05-26 16:36 root@box3 sabo]# yum list yum\* Loading "installonlyn" plugin Loading "rhnplugin" plugin Setting up repositories rhel-x86_64-server-5 100% |=========================| 1.4 kB 00:00 rhel-x86_64-server-cluste 100% |=========================| 1.4 kB 00:00 rhel-x86_64-server-cluste 100% |=========================| 1.4 kB 00:00 rhel-x86_64-server-vt-5 100% |=========================| 1.4 kB 00:00 rhn-tools-rhel-x86_64-ser 100% |=========================| 1.2 kB 00:00 Reading repository metadata in from local files rhel-x86_6: ################################################## 5337/5337 rhel-x86_6: ################################################## 81/81 rhel-x86_6: ################################################## 103/103 rhel-x86_6: ################################################## 124/124 rhn-tools-: ################################################## 371/371 Installed Packages yum.noarch 3.0.1-5.el5 installed yum-metadata-parser.x86_64 1.1.2-2.el5 installed yum-metadata-parser.x86_64 1.0-8.fc6 installed yum-rhn-plugin.noarch 0.5.2-5.el5_1.2 installed yum-updatesd.noarch 3.0.1-5.el5 installed Available Packages yum.noarch 3.2.8-9.el5_2.1 rhel-x86_64-serv yum-aliases.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-basearchonly.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-changelog.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-downloadonly.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-filter-data.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-kmod.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-list-data.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-protect-packages.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-protectbase.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-rhn-plugin.noarch 0.5.3-6.el5_2.6 rhel-x86_64-serv yum-security.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-skip-broken.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-updateonboot.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-updatesd.noarch 1:0.9-2.el5 rhel-x86_64-serv yum-utils.noarch 1.1.10-9.el5 rhel-x86_64-serv yum-versionlock.noarch 1.1.10-9.el5 rhel-x86_64-serv Can you try removing this: yum-metadata-parser.x86_64 1.0-8.fc6 installed ...and then doing the "clean all" followed by an update command The command to do that would be: yum remove yum-metadata-parser-1.0-8.fc6 ...or dito. with "rpm -e". Did not change behavior. Also note, that this has happened on several machines I attempted to update at the same time. Manually updating to yum-3.2.8-9.el5_2.1.noarch fixed it. Seems that an update got interrupted, and left it in a broken state. Do they all have the new and old versions of yum-metadata-parser? Yes, they do. (In reply to comment #7) > Also note, that this has happened on several machines I attempted to update at > the same time. Did the initial update complete without error (When you updated the whole system)? If that initial updated failed, did you notice if these multiple machines had the yum update fail on the same package? Any idea what yum was doing (what package was being updated/installed) at the time of the failure? Setting 5.3 to "?" so this shows up on queries .. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. (In reply to comment #8) > Manually updating to yum-3.2.8-9.el5_2.1.noarch fixed it. Seems that an update > got interrupted, and left it in a broken state. What's the command incantation for recovery via manual update?....rpm?....yum? I'm now stuck in this state after a yum update of several hundred packages was interrupted. You can run "yum-complete-transaction" ... but alas. that assumes yum itself is still functional. Assuming yum isn't functional you want to do something like: rpm -qa | egrep 'yum|rpm' ...then, if it's like the cases I've seen, you'll have two yum-metadata-parser packages installed. You need to remove one of them (remove the newer one if you still have yum-3.0.1 and the older one otherwise -- using rpm -e). At which point yum/yum-complete-transaction should work again. This problem occurred because yum-metadata-parser was half-upgraded. We do not plan to update this again in the rhel5 stream, which means that the likelihood of this problem recurring is vanishingly low. So I'm closing this, with the caveat that if plans change and we have to update yum-metadata-parser, we'll be sure this case can't happen. |