Description of problem:
This server is running RHEL 5.4. It has been powered off since October, 2009. Today, I powered it back on and ran "yum update yum\*". Then, I ran "yum update". I got the following error after yum downloaded all of the packages:
ERROR with rpm_check_debug vs depsolve:
xen-libs is needed by (installed) xen-3.0.3-55.el5.i386
(1, [u'Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%205&component=yum'])
Version-Release number of selected component (if applicable):
*Note* Red Hat Network repositories are not listed below. You must run this command as root to access RHN repositories.
Installed: rpm-22.214.171.124-18.el5.i386 at 2009-09-03 17:44
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2009-07-24 05:56
Committed: Panu Matilainen <email@example.com> at 2009-07-24 22:00
Installed: yum-3.2.22-26.el5.noarch at 2010-05-24 13:59
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2010-02-23 16:50
Committed: James Antill <firstname.lastname@example.org> at 2010-02-23 22:00
Installed: yum-metadata-parser-1.1.2-3.el5.i386 at 2009-09-03 17:38
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2009-04-06 14:15
Committed: James Antill <email@example.com> at 2009-04-06 22:00
Installed: yum-rhn-plugin-0.5.4-15.el5.noarch at 2010-05-24 14:00
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2009-12-21 11:59
Committed: Milan Zazrivec <firstname.lastname@example.org> at 2009-12-21 22:00
Very. I am unable to successfully run a "yum update"
Steps to Reproduce:
1. execute "yum update"
2. Observe failure
System software is not updated.
System software to be updated.
What do the following commands say:
yum list 'xen*'
# yum list 'xen*'
Loaded plugins: rhnplugin, security
xen.i386 3.0.3-55.el5 installed
xen-libs.i386 3.0.3-94.el5 installed
xen-libs.i386 3.0.3-105.el5_5.2 rhel-i386-server-5
# package-cleanup --problems
-bash: package-cleanup: command not found
FYI: The first (xen.i386) line was in red, the second (xen-libs.i386) was white, and the third line (xen-libs.i386 Available) was in blue.
Red is color_list_installed_extra, which means that "xen-3.0.3-55.el5" is not available from any repo.
And looking at the xen package you see:
% sudo repoquery --nevra xen
% sudo repoquery --requires xen | fgrep xen-libs
xen-libs = 3.0.3-105.el5
...but someone has force installed xen (or xen-libs) with a mismatched version. This means when yum comes to check it everything seems fine, because nothing requires the new version of xen ... but rpm sees that something is "wrong" and refuses to do anything.
If you enable a repo. which has xen, that will probably fix everything ... otherwise the only options are:
1. remove xen.
2. exclude the new xen-libs (it'll still be mismatched though).
3. use yumdownloader + rpm --force --nodeps to install the new xen-libs (not recommended).
I'm confused. I paid extra for a Red Hat Enterprise Linux subscription which supports Virtualization. Now, you're telling me that the only way to get a "yum update" to work is to uninstall xen? Won't that break Virtualization?
So, I guess I'd like to "probably fix everything" by enabling a repo containing xen. How do I do that?
Thanks in advance...
I can try and help, but bugzilla isn't the normal support channel and it's very possible that who you'd speak to using your normal support channel would be much better prepared to help you with enabling any repo(s). and/or subscriptions you are missing.
If you goto rhn.redhat.com and click on "systems" on the left menu bar, then click on the machine name that is having problems. Inside that page you should see something that says (IIRC, in the bottom left corner) what base channel and "sub-channels" your machine is subscribed to. That should list the virtualization channel (and I assume doesn't), assuming you still have a valid subscription to it then you should just be able to edit the channels and click to enable it as a sub-channel.
Then "yum repolist" on the client should list it and "yum list xen" on the client should list a newer xen package as available. "yum update xen\*" should then fix the rpmdb problem.