We create a "Baseline" channel that is sync'd nightly, so it always has the most recent patches. Then, on Patch Tuesday, we execute a spacewalk-clone-by-date to whatever that day is. We've had similar instances where a critical patch came out and our Security team wanted it in our channels immediately. With the clone channels it's simple to just add a particular Errata into it.
On Fri, Sep 26, 2014 at 7:34 AM, Glen Collins <[email protected]> wrote: > Hi All, > > I have a general question of the community on how everyone does their > patching. Here is what my company does.... > > Update the repository once a month on Microsoft Patch Tuesday. Keep that > as a baseline for the entire month so DEV, Test and Prod systems are > patched exactly alike. While this works pretty well, I do find some issues > with it. Like when an Errata's come out - My repository is not updated > until the next month. Which in turn I can miss out on patches which should > or need to be installed and unless I'm on the mailing lists, I'll miss it. > I have heard you can clone a channel and use that as a baseline and use the > regular channel to keep everything updated. > > So my question is, how does everyone else do this and do I have the > correct approach to clone the channel and use that as my baseline for the > patching and if need be, put the servers in the main group for any errata's > that come up. > > I would love to hear everyone thoughts on this. > > Thanks! > > Glen Collins > > _______________________________________________ > 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
