[Spacewalk-list] Upgrading SLES SP3 to SP4

[Daryl Rose]

Please ignore my last message.  I finally answered my own questions.


I'm not sure why the "test" SLES 11 SP3 severs were showing as being up-to-date, but I finally stop/started SW, and they started showing as needing updates.


I did an upgrade of one on those test machines from an ISO image.  We decided to perform all upgrades via ISO image, and not from SW,  so I wanted to test using the method that was agreed on.  After the upgrade was completed, I changed the channel to SLES 11 SP4/SLES 11 SP4 Updates.  I issued a "zypper ref" to refresh the repositories on the client, and they are now requiring updates from the new channels.


Thank you for the help.  It is very much appreciated.


Daryl


________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Daryl Rose <darylrose at outlook.com>
Sent: Tuesday, October 6, 2015 10:06 AM
To: Robert Paschedag; spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


I have a couple of questions.


1.  The command "zypper dup" say's that it performs a distribution upgrade.  Are you suggesting that I upgrade this way?

2.  I'm currently testing with a couple of test servers that I have.  I did a fresh install of SLES 11 SP3, registered it with my SW server, but it registered as "System is up-to-date".


I know this server needs updates.  I can run "zypper lu" and see that it needs a number of updates.

Yet, SW still claims that it is up-to-date.  I have a handful of other server, SLES 11 SP3, and all registered exactly the same, and all show that they require updates.  I can't figure out why these test servers are different.

Thanks.

Daryl



________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Robert Paschedag <robert.paschedag at web.de>
Sent: Tuesday, October 6, 2015 12:14 AM
To: spacewalk-list at redhat.com
Cc: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list]   Upgrading SLES SP3 to SP4


Hi Daryl,


I would just change the channels of the clients from SP3 to SP4 and then run a "zypper dup" on the clients.


This is how I upgraded clients from SP2 to SP3.


Regards

Robert





Versendet mit der SolMail-App<http://mail.sol.daum.net?via=mail_sign>

[http://i1.daumcdn.net/mimg/solstudio/resources/facebookLink_studio3.png]<http://mail.sol.daum.net/?via=mail_sign>

SolStudio
We try to shine your life like a gleaming sun with the essential services. Make your day even brighter with SolStudio apps.
Read more...<http://mail.sol.daum.net/?via=mail_sign>





--------- Original Message ---------
From: Daryl Rose
To: "spacewalk-list at redhat.com"
Date: Mon Oct 05 22:46:47 MESZ 2015
Subject: [Spacewalk-list] Upgrading SLES SP3 to SP4

How is the best way to change a SW repository?


We are in the process of upgrading our SLES servers to SP4.  I registered a few of the SP3 machines to the SW server.  I took one of those registered SP3 machines, deleted it from SW, upgraded it to SP4, then attempted to re-register using the SP4 activation key.  That didn't work so well.  I had to completely clean out all of the rhn and spacewalk packages from the client, re-install from the spacewalk repository.  I basically had to go back through all of the steps in registering a server to get it to register to the SP4 repositories.


Is there an easier way to change the repository?


Thanks


Daryl

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20151006/a851eacc/attachment.htm>