Why don't you save all important configs and any database with tar, move them
off the server in question and then pop in a 5.5 iso/cdrom and do an an
upgrade? Curiously, why not upgrade to 5.10 or 5.11? RedHat does not even still
support 5.6.
When you boot up with the iso or cdrom, you will be presented with option to
either install new or upgrade existing system. Choose upgrade. After upgrading
you can then do a subscription to the desired channels (5.5). On the SW webUI,
then do a software upgrade. In /etc/yum.repos.d remove all old 5.4 *.repo
files, rm -rf /var/cache/yum, yum clean all, yum makecache, yum update/upgrade
Subscribing 5.4 to a 5.5 software channel has not worked for me. Oh yes, you
can make today a great day! Thanks.
Very Respectfully,
A. C. Kebei
Always, Very Committed to Excellence and the fair treatment of all.
From: "Reneau, Wes W [HDS]" <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Wednesday, December 10, 2014 10:38 AM
Subject: [Spacewalk-list] upgrade client from 5.4 to 5.5
<!--#yiv6680748526 .yiv6680748526EmailQuote
{margin-left:1pt;padding-left:4pt;border-left:#800000 2px solid;}-->I’ve
bounced around on google but haven’t found the right syntax to find a valid hit
that explains how I might upgrade one “.” revision. In this case I have RHEL
5.4 server I’d like to upgrade to 5.5. I modified its base channel from 5.4 to
the 5.5 w/ all its dependencies and tried an upgrade in spacewalk only to find
it failed w/ conflicts from rhn-client-tools and up2date and so on. Is there a
best practice someone can point me to or recommendations? Thanks Wes
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
