For this sort of instance, I created a Zero Day patch channel all my systems are subscribed to, and simply clone the critical erratas to this channel as needed.
On Tue, Jun 16, 2015 at 1:09 PM, Robert Paschedag <[email protected]> wrote: > I think I would subscribe the channel, apply the patch and unsubscribe > again. Thus should work with action chains.Am 16.06.2015 7:31 nachm. > schrieb "Clegg, Larry E [HDS]" <[email protected]>: > > > > Greetings Spacewalkers, > > > > > > > > I have a process question for you. Here’s the setup: > > > > > > > > You have your systems setup in Spacewalk and subscribed to channels that > are frozen in time, e.g. some systems are subscribed the channels with all > the Q2 patches and updates. Other systems may still be subscribed to the > Q1 patches and updates. You have your latest channels that are sync’d with > the vendor’s latest offerings but no systems are subscribed to these > “latest” channels. > > > > > > > > Let’s say a vendor (Redhat, Oracle, etc) releases a critical bug fix > patch to their “latest” channel. Let’s say you want to deploy this > critical bug fix asap – even though it is out of step with your quarterly > patching cycle. You have a system that is subscribed to a channel tree > that is frozen in time, for example a system is subscribed to your Q2 > patches. You’re not ready to update everything yet but you do want this > one critical bug fix patch (and any dependencies) to be made available to > this system. > > > > > > > > How do you go about handling this type of situation? > > > > > > > > Thanks, > > > > > > > > Larry > > > > > > > > Larry Clegg > > > > HD Supply San Diego > > > > EMail: [email protected] > > > > > > _______________________________________________ > 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
