RHEL update strategy question
 

Given RHEL and subscriptions to RH network (but no other RH purchased products, like satellite server), and totally identical hardware configurations:

1. You use up2date to update your test box.
2. You play with the test box for a few weeks.
3. You then want to say "put the same rpm updates onto my production box that the test box got, but don't put any newer updates on that box."

I could do this with scripts (having retained the rpms the original up2date had downloaded), but that seems like an ugly solution, so I'm looking for the obvious way to do this that I'm missing.

Thanks

Paul

You could just setup a local rpm repository and configure your client machines to grab updates from there. Then you can push update packages to the local update repo once you've tested them. Make sure to push critical updates out to the clients ASAP otherwise you could get yourself into trouble.

The RHN Satellite module does this for you. Although, we opted out of this for our own custom scripts.