Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Migrating systems from RHN to RHNSM

News RHEL subscription management Recommended Books Recommended Links Migrating systems from RHN to RHNSM Registering a server using Red Hat Subscription Manager (RHSM) Redhat Networking  Unix Administration
RHEL4 registration RHEL5 registration on proxy protected network RHEL6 registration on proxy protected network  Oracle Linux Registration Xinetd How to change IP address in RHEL Humor Etc

"New" subscription system (RHSM) is slightly better then RHN for large organizations.  It allows to assign specific license to specific box and list the current status of licensing.  But like RHN it requires to use proxy setting in configuration file, it does not take them from the environment. If the company has several proxies and you have mismatch you can be royally screwed. In general you need already to check consistently of your environment with conf file settings.  The level of understanding of proxies environment by RHEL tech support is basic of worse, so they are  using the database of articles instead of actually troubleshooting based on sosreport data. Moreover each day there might a new person working on your ticket, so there no continuity. RHEL System Registration Guide (https://access.redhat.com/articles/737393) is weak and does not cover more complex cases and typical mishaps.

On RHEL 6 subscription-manager is preinstalled.  If you run RHEL 6.2 or below you need to update the package before proceeding.  It can be done form ISO.

There are two cases of migration: your subscription expired and you subscription is current. If your subscription expired you have twp options:

Enabling subscription manager and then disabling RHN

For some reason migration to RHNSM is easier then the registration from scratch.  The following steps are

# subscription-manager register 

# subscription-manager list --available --all

Above command will give you list of available subscriptions and pool ID. You will need to copy the pool id that you want to attach to the system

# subscription-manager attach --pool=

Once done you can check the subscription status by executing below command:

# subscription-manager list --consumed
This command allows you to check if system is registered, attached to it subscriptions and expiration date
# yum clean all
From the yum manual:

"CLEAN OPTIONS
The following are the ways which you can invoke yum in clean mode.

yum clean packages

Eliminate any cached packages from the system. Note that packages are not automatically deleted after they are downloaded.

yum clean headers

Eliminate all of the files which yum uses to determine the remote availability of packages. Using this option will force yum to download all the headers the next time it is run.

yum clean all

Runs yum clean packages and yum clean headers as above."

The "yum clean all" command will not only remove cached packages, but also any headers. You need flush out everything in case there are obsolete headers

# yum repolist # (or if you want to see all avalable repositories yum repolist all )

Now you can see to what repositories you are subscribed and if you wish what repositories are available for subscription.

Once this is done, you can un-register the system from RHN Classic. To do this you need to do two things:

Now can also try to install or update one package on the system to see if it works

yum update vim

If this command failed you need to enable repositories

See How to add a new yum repository

Recommended by Red Hat migration process

Do not try this if your subscription si alreay expred. Those packages have a lot of dependencies that you will never be able to resove without much pain.

  1. The migration tools and data are usually in the main channels for Red Hat Enterprise Linux 5 or 6, but they may be located in optional or supplementary channels. Do a simple yum search to make sure that the packages are available. For example:
    [root@server ~]# yum search subscription-manager-migration -v
    Not loading "rhnplugin" plugin, as it is disabled
    Loading "product-id" plugin
    Loading "refresh-packagekit" plugin
    Loading "security" plugin
    Loading "subscription-manager" plugin
    Updating certificate-based repositories.
    
    ================= N/S Matched: subscription-manager-migration ==================
    subscription-manager-migration.x86_64 : Migration scripts for moving to
                                          : certificate based subscriptions
    Repo        : rhel-6-server-rpms
    
    subscription-manager-migration-data.noarch : RHN Classic to RHSM migration data
    Repo        : rhel-6-server-rpms
    If necessary, enable the supplementary repositories which contain the migration RPMs.
    [root@server ~]# subscription-manager repos --enable rhel-6-server-optional-rpms
  2. Install the migration tool packages.
    [root@server ~]# yum install subscription

    or

    # yum install subscription-manager-migration subscription-manager-migration-data
  3. Run migration tool
    # rhn-migrate-classic-to-rhsm

    More information on migrating systems from RHN Classic to Certificate-based RHN can be found in our official Subscription Management Guide.

    An alternate, manual and unsupported method 

    For the migration process the system should only be subscribed to base channel. If it is subscribed to any child channels, remove the child channels before the migration process.

    Check if you are still subscribed to RHN Classic:

    [root@localhost ~]# yum check-update
    Loaded plugins: refresh-packagekit, rhnplugin
    

    2. Install plugins needed for RHSM (not necessary for RHEL 6)

    [root@localhost ~]# yum install subscription-manager
    

    3. Change directory to edit plugins.

    [root@localhost ~]# cd /etc/yum/pluginconf.d
    

    4. List current plugins

    [root@localhost pluginconf.d]# ls
    refresh-packagekit.conf rhnplugin.conf
    

    5. Edit plugins on system, enable plugins needed for RHSM

    [root@localhost pluginconf.d]# vim rhnplugin.conf
    [main]
    enabled = 0
    gpgcheck = 1
    

    6. Clean yum

    [root@localhost pluginconf.d]# yum clean all
    Loaded plugins: refresh-packagekit, rhnplugin
    Cleaning up Everything
    

    7. Remove (or rename) the systemid file

    [root@localhost ~]# cd /etc/sysconfig/rhn
    [root@localhost ~]# mv systemid rhnclassic.systemid
    

    8. Register system to RHSM via command-line

    [root@localhost pluginconf.d]# subscription-manager register --autosubscribe

    Top Visited
    Switchboard
    Latest
    Past week
    Past month

    NEWS CONTENTS

    Old News ;-)

    Migrating from RHN Classic

    For both Red Hat Enterprise Linux 5 and 6, migrating a system's registration and subscriptions from RHN Classic Hosted to Customer Portal Subscription Management (hosted) uses the rhn-migrate-classic-to-rhsm migration script.

    Subscription Concepts and Workflows" outlines the importance of clear, detailed, and consistent subscription tracking. It is an increasingly critical part of IT maintenance. The older channel-based subscription management process in RHN Classic was great at providing access, but it was very difficult to get an accurate accounting of how subscriptions were applied, how many subscriptions were being used, where subscriptions were being used, and what any individual system was using.

    The migration process involves moving the system's full registration information - including its subscriptions - from RHN Classic to Customer Portal Subscription Management. The system is identified by a unique number. This can either be a systemid value (Red Hat Enterprise Linux 5 or 6) or an installation number (Red Hat Enterprise Linux 5).

    The migration script takes the identifier and then uses it to extract and migrate the system entry. rhn-migrate-classic-to-rhsm performs the migration based on the system ID, in the /etc/sysconfig/rhn/systemid file.

    2.2. Installing the Migration Tools

    The migration tools are contained in the subscription-manager-migration package. An additional package, subscription-manager-migration-data, is required to map the RHN Classic channels to Customer Portal Subscription Management product certificates.
    1. The migration tools and data are usually in the main channels for Red Hat Enterprise Linux 5 or 6, but they may be located in optional or supplementary channels. Do a simple yum search to make sure that the packages are available. For example:
      [root@server ~]# yum search subscription-manager-migration -v
      Not loading "rhnplugin" plugin, as it is disabled
      Loading "product-id" plugin
      Loading "refresh-packagekit" plugin
      Loading "security" plugin
      Loading "subscription-manager" plugin
      Updating certificate-based repositories.
      
      ================= N/S Matched: subscription-manager-migration ==================
      subscription-manager-migration.x86_64 : Migration scripts for moving to
                                            : certificate based subscriptions
      Repo        : rhel-6-server-rpms
      
      subscription-manager-migration-data.noarch : RHN Classic to RHSM migration data
      Repo        : rhel-6-server-rpms
      If necessary, enable the supplementary repositories which contain the migration RPMs.
      [root@server ~]# subscription-manager repos --enable rhel-6-server-optional-rpms
    2. Install the migration tool packages.
      [root@server ~]# yum install subscription

    Recommended Links

    Google matched content

    Softpanorama Recommended

    Top articles

    Sites

    Top articles

    Sites

    ...

    Migrating from RHN Classic



    Etc

    Society

    Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

    Quotes

    War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

    Bulletin:

    Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

    History:

    Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

    Classic books:

    The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

    Most popular humor pages:

    Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

    The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D


    Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

    FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

    This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

    You can use PayPal to to buy a cup of coffee for authors of this site

    Disclaimer:

    The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

    Last modified: October, 18, 2019