How do I access Red Hat Enterprise Linux 4 Extended Life Cycle Support (ELS) content after Red Hat Enterprise Linux 4 transitions to Extended Life Phase?

Updated -

Issue

  • How do I access Red Hat Enterprise Linux 4 Extended Life Cycle Support content after Red Hat Enterprise Linux 4 transitions to Extended Life Phase?

Environment

  • Red Hat Enterprise Linux 4

  • Red Hat Network (RHN) Classic or Red Hat Network (RHN) Satellite

Resolution

On March 01, 2012 Red Hat Enterprise Linux 4 transitions from Production phase to Extended Life Cycle phase. You can read more about product life cycles here. At this time, Red Hat Enterprise Linux 4 content will continue to be accessible in the same way as it always has been via Red Hat Network (RHN) Classic and RHN Satellite.

If you have purchased the Red Hat Enterprise Linux 4 Extended Life Cycle Support (ELS) Add-On offering, you will receive continued updates for Red Hat Enterprise Linux 4 via a new child channel under the Red Hat Enterprise Linux 4 base channel in Red Hat Network (RHN) Classic and Red Hat Network (RHN) Satellite. Follow these steps to access Red Hat Enterprise Linux 4 Extended Life Cycle Support (ELS) content:

For Red Hat Network (RHN) Classic users:

If you have purchased an Red Hat Enterprise Linux 4 Extended Life Cycle Support (ELS) Add-On subscription, you can access the ELS content manually or using the Red Hat Network (RHN) API.

Step 1. To manually subscribe, click on the system profile that needs ELS.

Step 2. Click on the blue "Alter Channel Subscriptions" link.

Step 3. Under "Software Channel Subscriptions" section do the following based on what kind of system you have i.e. x86, x86_64, or Itanium:

  • Step 4 for IA-32. If you have an IA-32 system, uncollapse the link "Additional Services Channels for Red Hat Enterprise Linux 4 for IA-32".

    • Step 5 for IA-32. Select either the child channel "Red Hat Enterprise Linux AS ELS (v. 4 for x86)" or "Red Hat Enterprise Linux ES ELS (v. 4 for x86)".
  • Step 4 for x86_64. If you have a x86_64 system, uncollapse the link "Additional Services Channels for Red Hat Enterprise Linux 4 for x86_64".

    • Step 5 for x86_64. Select either the child channel "Red Hat Enterprise Linux AS ELS (v. 4 for 64-bit x86_64)" or "Red Hat Enterprise Linux ES ELS (v. 4 for 64-bit x86_64)".
  • Step 4 for IA-64. If you have an Itanium (IA-64) system, uncollapse the link "Additional Services Channels for Red Hat Enterprise Linux 4 for IA-64".

    • Step 5 for IA-64. Select the child channel "Red Hat Enterprise Linux AS ELS (v. 4 for Itanium)".

You may also choose to use an Red Hat Network (RHN) API call to update your system profile subscriptions.

For Red Hat Network (RHN) Satellite users:

After you purchase a Red Hat Enterprise Linux 4 Extended Life Cycle Support (ELS) subscription, contact Red Hat Global Support Services (by phone or by opening an online ticket) and request a new Satellite certificate that contains your ELS products. Once you have a new Satellite certificate, you will need to activate the new certificate on your Satellite.

With Red Hat Enterprise Linux 4 ELS available, you will use the satellite-sync command to import the new Red Hat Enterprise Linux 4 ELS child channels into your Satellite.

Once the new Red Hat Enterprise Linux 4 ELS child channel is imported, for those systems which will consume ELS, subscribe the Ret Hat Enterprise Linux 4 systems to the new child channels and continue to manage them as normal.

If your Red Hat Enterprise Linux 4 ELS systems are subscribed to custom or cloned base channels, you will need to similarly clone the new Red Hat Enterprise Linux 4 ELS child channels to make available to your systems.

NOTE:
* If no action is taken, Red Hat Enterprise Linux 4 Systems that are registered to Satellite but have no ELS access will continue to consume an entitlement and have access to pre-ELS released Red Hat Enterprise Linux 4 Errata, Kickstart trees, and packages.
* If the RHN Satellite server itself is running on Red Hat Enterprise Linux 4, you will need to upgrade the Satellite since RHN Satellite and Proxy 5.x on Red Hat Enterprise Linux 4 enter end-of-life on December 1st, 2012. Please see End-of-Life (EOL) notification for RHN Satellite 5 running on Red Hat Enterprise Linux 4.

2 Comments

For folks that have to provide ELS 4 packages in a disconnected mode, you systems aren't connected to a satellite server or RHN.

Option #1
Go to rhn and get them

https://rhn.redhat.com/rhn/software/channels/All.do

Make sure the following filter is set correctly

"Filter by Production Channel:"

Red Hat Enterprise Linux ELS

Option #2
Hook a system on not within your DMZ zone that is ok to get access to RHN or Satellite

For systems that you need to update within your dmz, pull an rpm listing like so from a node in your dmz
right_now=$(date +"%Y%m%d%H%M%S"); rpm -qa --qf '%{name}.%{arch}\n' | sort | uniq > /tmp/$(hostname)_${right_now}_rpms.txt

Assuming all your nodes have the same package set, otherwise you may need to for ones that differ.

Now going back to your system that has access to Satellite or RHN run this script.

#!/bin/bash

right_now=$(date +"%Y%m%d%H%M%S")

#first pull and rpm listing
rpm -qa --qf '%{name}.%{arch}\n' > /tmp/$(hostname)_${right_now}_rpms.txt

dest_dir=$1

your_release=$2

if [ ! -d $dest_dir ]
then
echo "This directory ( $dest_dir ) does not exist, exiting"
exit 1
else

while read rpm
do
yumdownloader --resolve --destdir="${dest_dir}" $rpm | tee -a patchset-${your_release}-${right_now}.log
done < /tmp/<filename_from_above>
#make sure you change the filename to be correct it's the one we created above, you could add a $3 and pass it in

fi

Then once you have the updated package set you can now create a create a yum repo and sneakernet your yum remove and yum repo config file over to your dmz nodes.

For generating a yum repo, you would want to use the rpm directory dump created from the script above
https://access.redhat.com/knowledge/solutions/7227