Update from offline local repository with a predefined release.
Hi all,
i have a lab which is consisted of 3 servers. One as management (No internet connection. Acts as offline repository), one as remote (No internet connection) and one for getting all the latest updates from RHN (Online updater).
I would like to keep the remote one updated on a specific version (7.2) by "locking" it's kernel's release using the following commands:
subscription-manager --release=7.2
yum clean all
It's .repo files stored in "/etc/yum.repos.d" are edited and the baseurl points to management servers' HTTP server where all the latest repo packages are residing (after transferred from online updater).
Problem:
Even though all machines have been registered with a valid RHEL Server EUS subscription and even though release is set to 7.2, when remote is updated it's kernel gets upgraded to 7.5.
Notes:
I have removing the contents of folder "/var/cache/yum" and then "yum clean all" but result is the same.
Is the feature of setting a RHEL release working only when updating while being online and downloading from RHN?
Any help would be appreciated.
Thanks
Responses
Hi IG ! :)
I've read your other post, where you seem to have it solved by removing yum cache and cleaning up yum following the suggestions from Sadashiva. What you describe here is only possible when the downloaded repository content on your external server contains these newer kernel packages, or when something is not correctly configured in the .repo files in the /etc/yum.repos.d folder.
Regards,
Christian
Hi IG,
You have to decide it yourself ... either receiving the latest stable updates or stick with 7.2 EUS. :)
You can exclude specific packages though - example : sudo yum update --exclude=kernel*
Regards,
Christian
IG,
EUS enables to stay on with same minor version and still receive updates,, check this KB for more details https://access.redhat.com/solutions/22763. https://www.redhat.com/en/about/red-hat-enterprise-linux-extended-update-support-eus-package-inclusion-list
Hi IG,
Apart from what Christian has suggested, I'm confused on how the remote system (one without internet) has been set with locking version using "subscription-manager --release=7.2"? Could you explain more about this...
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
