Well, I tried using the "Always use the newest Tree for this base channel" setting a week or so back, with the existing channels/repos. It did cause the outstanding package updates at the time to get used during kickstart. Subsequent updates did not picked up for kickstart, though.
On Mon, Mar 14, 2016 at 8:29 AM, William H. ten Bensel <[email protected]> wrote: > Could it be that a new distribution needs to be created and the kickstart > profile should have "Always use the newest Tree for this base channel" > > - Thanks and good luck > > > > > From: Noah Rømer <[email protected]> > To: [email protected] > Date: 03/11/2016 11:41 AM > Subject: Re: [Spacewalk-list] old package versions installed > during kickstarts > > Sent by: [email protected] > ------------------------------ > > > > This email originated from outside of the company. Please use discretion > if opening attachments or clicking on links. > ------------------------------ > > > We just have the one kickstart profile, with activation keys for a group > of repositories including upstream Cetnos and a repository for our internal > code. > > On Thu, Mar 10, 2016 at 6:41 AM, William H. ten Bensel <*[email protected]* > <[email protected]>> wrote: > 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* > <https://bugzilla.redhat.com/show_bug.cgi?id=1280167> > > - Thanks and good luck > > > > From: Noah Rømer <*[email protected]* <[email protected]>> > To: *[email protected]* <[email protected]> > Date: 03/09/2016 05:02 PM > Subject: [Spacewalk-list] old package versions installed during > kickstarts > Sent by: *[email protected]* > <[email protected]> > ------------------------------ > > > > 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 > *[email protected]* <[email protected]> > *https://www.redhat.com/mailman/listinfo/spacewalk-list* > <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. > > ** > > _______________________________________________ > Spacewalk-list mailing list > *[email protected]* <[email protected]> > *https://www.redhat.com/mailman/listinfo/spacewalk-list* > <https://www.redhat.com/mailman/listinfo/spacewalk-list> > > > > -- > 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 > [email protected] > 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. > > ** > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > -- Squirrels are the lunatic teenagers of the animal kingdom.
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
