Upgrade from RedHat 7.3 to RedHat 7.4
Hello,
I seem to have an issue in that when I try to upgrade a Redhat Server 7.3 to 7.4 it is not doing the upgrade. I connect to a RedHat Satellite 6.2 server and I thought it would be transparent. I was able to upgrade to 7.3 without any issues.
This is how my redhat.repo looks:
[rhel-7-server-rpms]
metadata_expire = 1
sslclientcert = /etc/pki/entitlement/1337237208733725132.pem
baseurl = https://rhs1v.xxx/pulp/repos/xxxx/Library/content/dist/rhel/server/7/7.3/$basearch/os
ui_repoid_vars = basearch
sslverify = 1
name = Red Hat Enterprise Linux 7 Server (RPMs)
sslclientkey = /etc/pki/entitlement/1337237208733725132-key.pem
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
enabled = 1
sslcacert = /etc/rhsm/ca/katello-server-ca.pem
gpgcheck = 1
Any thought of what I am missing? Should it not be transparent to do the upgrade and be able to take the updates or am I miising something in my satellite configuration.
Any help is greatly appreciated.
Responses
Red Hat
Guru
2305 points
Looking at the baseurl https://rhs1v.xxx/pulp/repos/xxxx/Library/content/dist/rhel/server/7/7.3/$basearch/os, you can see that this system is locked to a particular release (7.3 in your case). This repository type contains ONLY RHEL content from GA until the day before RHEL 7.4 is released. (Basically 7.3 and nothing more)
This explains why you do not see updates and cannot update to 7.4. A couple of way resolve this:
- Option 1: switch to a 7.4 repo.
- Option 2: switch to the 7Server repo. (The 7Server repo is the 'always updated' version of RHEL)
In either scenario you'd:
- enable & sync the repo in Satellite
- Switch the client to the required release version
enable & sync the repo in Satellite
ORG=Example
RELEASE=7Server
hammer repository-set enable \
--organization "$ORG" \
--product 'Red Hat Enterprise Linux Server' \
--basearch='x86_64' \
--releasever='$RELEASE' --name 'Red Hat Enterprise Linux 7 Server (RPMs)' `
hammer repository synchronize \
--organization "$ORG" \
--product 'Red Hat Enterprise Linux Server' \
--name "Red Hat Enterprise Linux 7 Server RPMs x86_64 ${RELEASE}" \
--async
enable the repo on the client
RELEASE=7.4
subscription-manager release --set $RELEASE
More on the different repository types can be found in Understanding Red Hat Content Delivery Network Repositories and their usage with Satellite 6
Red Hat
Guru
2305 points
On your Satellite Server, you have both (7.3 & 7.4) repos enabled, meaning that Satellite will sync both of them. However, a client can have exactly 1 release version. That is, you cannot have both the 7.3 & 7.4 repos enabled simultaneously. (bad things re: dependency resolution happen if you do). That explains why you were able to update once you changed the release version via the subscription-manager command.
Hi Rich. I have a similar question. I have local repositories on the server. I do not call out to the internet to pull down the latest updates. How can I avoid updating the OS to the latest version? For example, if I am upgrading from 7.3 to 7.4, I don't want the server to automatically upgrade to 7.5 when the update is available in the same repository. I've tried yum --releasever=7.4 update (https://access.redhat.com/solutions/238533) but it still updates to 7.5. Any advice?
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.