Locking RPM versions within the latest minor release across multiple hosts

Latest response

Hi,

We know that we can lock a certain minor release version using "SM release --set=7.x". But is there a possibility to lock/ always update to a certain state of RPM packages within that release, across a set of machines?

Example:
A company's "OS patching cycle" starts on 1st Jan and continues for 3 months. During those 3 months "yum update" provides different results on multiple machines as new pkgs become available during the course of those 3 months.

Is there a way, so that "yum update" installs the same set of pkgs on 25th March and 1st Jan.

Is it only possible using Satellite?

Thanks,
Junaid.

Responses

Just to add further, the same functionality could be achieved consistently on Solaris 11 using the concept of SRUs, though SRU 29 is available, we could instead upgrade to SRU 25 using:

pkg   update   entire@0.5.11-0.175.0.3.25.0.0

I think this functionality is not available on RPM based systems.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.