[Spacewalk-list] old package versions installed during kickstarts

William H. ten Bensel WHTENBEN at up.com
Thu Mar 10 14:41:51 UTC 2016


We do this, however it is by design.  Hopefully this will help.

It is accomplished by:

A Kickstart profile is pointed to a "clone-by-date" base channel, updates, 
extras, debuginfo, and spacewalk-client.   This gives us 6.1, 6.2, 6.5, 
6.5r1, 6.5r2, 6.6, kickstarts.
        Systems->kickstart->profiles-> "profile" -> Kickstart details -> 
Operating system
The same Kickstart profile has an activation key that is pointed to the 
updated version base channel, updates, extras, debuginfo, and 
spacewalk-client.
        Systems->kickstart->profiles-> "profile" ->Activation Keys -> 
"activation key" -> Child Channels

So, if the kickstart profile 6.4 is used, the older packages are 
installed.  Then the activation key is applied with the updated channels 
which allows the newer packages to be available but not installed during 
kickstart.  The Admin/application team is then able to determine when the 
best time would be to update the system.

Caution:  If you are cloning the spacewalk-client channel and doing it 
this way  https://bugzilla.redhat.com/show_bug.cgi?id=1280167

- Thanks and good luck



From:   Noah Rømer <baronmog at gmail.com>
To:     spacewalk-list at redhat.com
Date:   03/09/2016 05:02 PM
Subject:        [Spacewalk-list] old package versions installed during 
kickstarts
Sent by:        spacewalk-list-bounces at redhat.com



This email originated from outside of the company. Please use discretion 
if opening attachments or clicking on links. 
We're using Spacewalk 2.2 (on CentOS 6.6 servers) to handle kickstart 
profiles and channels.

If I update a package in one of the channels/yum repositories, after doing 
a spacewalk-repo-sync for the channel, the new version shows up as an 
available update, but the old version is still installed when a new system 
is kickstarted.

Any ideas on what would cause this? There is a http proxy and a spacewalk 
proxy in front of the spacewalk server, but restarting the proxies doesn't 
fix the issue. Often times, the issue will go away after a few days/weeks, 
but I can't connect it to a specific action. That makes me think there's 
some cache somewhere that I haven't yet found.

-- 
Squirrels are the lunatic teenagers of the animal kingdom.This email 
originated from outside of the company.  Please use discretion if opening 
attachments or clicking on links.

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


**

This email and any attachments may contain information that is confidential and/or privileged for the sole use of the intended recipient.  Any use, review, disclosure, copying, distribution or reliance by others, and any forwarding of this email or its contents, without the express permission of the sender is strictly prohibited by law.  If you are not the intended recipient, please contact the sender immediately, delete the e-mail and destroy all copies.
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160310/8dfdf4a6/attachment.htm>


More information about the Spacewalk-list mailing list