What channels should be used for RHEV 3.6 ELS?

Environment

• RHEV 3.6

Issue

• RHEV 3.x is retired now, I purchased RHEV 3.6 ELS plan.
• What channels should I configure to keep my environment up and running?

Resolution

If ELS plan is purchased, make sure to configure the manager and the RHEL hosts with the following channels:

For manager:

# subscription-manager repos --disable=* \
    --enable=rhel-6-server-rpms \
    --enable=rhel-6-server-supplementary-rpms \
    --enable=jb-eap-6-for-rhel-6-server-rpms \
    --enable=rhel-6-server-rhevm-3.6-els-rpms \
    --enable=rhel-6-server-rhevm-3.6-rpms 

For RHEL hypervisors:

# subscription-manager release --set=7.3
# subscription-manager repos --disable=* \
     --enable=rhel-7-server-eus-rpms \
     --enable=rhel-7-server-rhev-mgmt-agent-rpms \
     --enable=rhel-7-server-rhev-mgmt-agent-els-rpms
# yum clean all
# rm -rf /var/cache/yum/*

If any RHEL-7.4 packages are present on 3.6 host for any reason, make sure to downgrade them with yum distro-sync.

For RHEV-H (thin hypervisor):
Nothing is needed. RHEVH is provided as an ISO image and can't pull updates for this host from CDN.

If ELS plan is not purchased, it is recommended to lock the RHEL host to 7.3 release, to prevent accidental upgrade of the hosts to 7.4 and higher.

# subscription-manager release --set=7.3

Consider migrating your environment to RHV 4, as RHEV 3.6 is retired. For additional information check RHV Life Cycle Page.

General information about EUS and locking a version to a specific release can be found here:
How to tie a system to a specific update of Red Hat Enterprise Linux? .

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.