Unable to lock release using subscription-manager

Latest response

We have to test new storage devices against several rhel releases/versions. Therefore, I use subscription-manager to lock the release. I’m able to list available releases on 6.* and 7.1, but not 7.0 Secondary issue: I just received a new batch of licenses so I’m going back and re-establishing some subscriptions which had recently been dropped. In this example I don’t know why the subscription thinks my image is 7.1 when the O/S indicates 7.0

Problem:
subscription-manager release --list
No release versions available, please check subscriptions.

subscription-manager release --set=7.0
No releases match '7.0'. Consult 'release --list' for a full listing.

Information:
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.0 (Maipo)

uname -r
3.10.0-123.13.2.el7.x86_64

subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.26.8-1
subscription-manager: 1.10.14-9.el7_0
python-rhsm: 1.10.12-2.el7

subscription-manager status | grep Overall
Overall Status: Current

subscription-manager list
Product Name: Red Hat Enterprise Linux Server
Product ID: 69
Version: 7.1
Arch: x86_64
Status: Subscribed
Status Details:
Starts: 03/02/2015
Ends: 03/02/2016

TK
Log in to join the conversation

Responses

Radek Bíba's picture Red Hat Guru 1517 points
23 March 2015 1:11 PM

Thomas,

I'm sorry, but Extended Update Support isn't available for RHEL 7.0. Can you update to 7.1?

Not sure why SM thinks you're running 7.1, but it's possible that it just takes your RHEL-7 system as 7.1 because that's the only supported RHEL-7 release at the moment.

Bryan Kearney's picture Red Hat Pro 755 points
23 March 2015 1:27 PM

What is the output of

subscription-manager facts --list | grep dist
TK Community Member 95 points
23 March 2015 3:16 PM

Radek,
I'm not looking for extended support. I'm simply trying to lock the release so a yum update won't automatically upgrade the system to 7.1 I normally do this with a command such as: subscription-manager release --set=6.5 However, this command will only work based on the results of: subscription-manager release --list

Bryan,
subscription-manager facts --list | grep dist
distribution.id: Maipo
distribution.name: Red Hat Enterprise Linux Server
distribution.version: 7.0
distribution.version.modifier: ga

DS Newbie 12 points
30 April 2015 8:50 PM

We have the exact same problem. We are evaluating software which requires 7.0, not 7.1. I would like to do so with up to date packages for 7.0 only - no upgrade to 7.1

We ge the same messages as OP:

subscription-manager release --set=7.0
No releases match '7.0'. Consult 'release --list' for a full listing.

subscription-manager release --list
No release versions available, please check subscriptions.

I would appreciate either a way to lock my version to 7.0 or method of doing package updates without changing version to 7.1

Thank you for your help.

DS Newbie 12 points
30 April 2015 11:03 PM

After looking around some more, I think I found a solution. It looks like the register option allows you to specify the release if you also use the auto-attach flag. So using a command like:

 subscription-manager register --auto-attach --release=7.0 --force

Will set the release to 7.0. Note that you have to specify the --force if you have already registered the instance.

After doing this, I get:

subscription-manager release --show
Release: 7.0

So the release --list and release --set commands are still broken, but at least there seems to be a workaround.

TK Community Member 95 points
1 May 2015 3:03 AM

I opened a case for my issue. I'm waiting for the next reply but here is the current summary as I "understand" them.
1. There is an update for the subscription-manager which resolves the ability to set the release-lock value.
2. It doesn't resolve the basic problem. Any yum update will begin to pull in 7.1 rpms
I'll spare you all the details but here's the core issue: RHEL 7.0 is no longer an active version, and Red Hat does not offer EUS support for 7.0 (as mentioned by Radek above, but I didn't understand the implications of his response)
Excerpt from: https://access.redhat.com/support/policy/updates/errata/
In Red Hat Enterprise Linux 7, EUS is available for the following releases:
7.0 (N/A)
7.1 (ends March 31, 2017)

SN Community Member 76 points
9 April 2017 8:03 AM

I've tried Doug Shelley's solution with 1 addition - I've added in yum.conf under the [main] section:

distroverpkg=X.Y It limits the packages up to latest of your distro version . In my case - 7.0

Edit: use the following during registration "subscription-manager register --auto-attach --release=7.0 --force"

Source: https://access.redhat.com/solutions/238533

DR Community Member 20 points
12 October 2018 7:04 PM

The article is helpful, I had an issue with forcing the command (subscription-manager register --auto-attach --release=5.8 --force) and unregistered the server instead. Seems the server is having trouble re-registering I may need to reboot it.
I am running these via a script, setting the minor release channel non-persistently will work better for our purposes. (yum --releasever=5.8 update)

Close

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