Tuesday, May 21, 2013

How to Change Channel Subscriptions for Servers


This document describes how to alter channel subscriptions for groups of servers. For example, we will clone an existing channel to rename it then unsubscribe all systems from that channel and subscribe to the new channel.

Part I:  Clone Existing Channel

1.       Login to Satellite and go to Channels > Manage Software Channels > clone channel
2.       On the New Channel page, select the channel you want to clone, (Old-channel) in our example, and choose ‘Current state of the channel (all errata) then click Create Channel
3.       Complete the following fields to clone the channel:
·         Parent Channel:       leave as is
·         Channel Name:         change to Wakkadoo Channel
·         Channel Label:          change to wakkadoo-channel
·         Architecture:             leave as x86_64
·         Channel Summary:  Wakkadoo Channel
·         Channel Description:  Enter description for channel.
4.       Click on Create Channel to create the new cloned channel.
5.       On the new channel page, enter any additional information, such as Maintainer Name, Email, and Support Policy.

Part II: Verify can install/remove packages on Test System

1   1.     Login to a dev box and run the following command to verify channel is    available.
·         # rhn-channel -L
Username: twalt
Password:

rhel-x86_64-server-ha-6
wakkadoo-channel

2.       Notice the channel is available so now verify the system is subscribed to Old-channel channel
·         # rhn-channel -l
                                                               i.      old-channel

3.       Unsubscribe from old-channel
·         # rhn-channel -r -c old-channel
·         # rhn-channel –l (to verify not listed)

4.       Subscribe to Wakkadoo Channel
·         # rhn-channel -a -c wakkadoo-channel

5.       Check that packages are ‘available’ from wakkadoo-channel
·         # yum list available ansible
·         Loaded plugins: product-id, rhnplugin, security, subscription-manager
·         Updating certificate-based repositories.
·         Unable to read consumer identity
·         wakkadoo-channel                                         |  871 B     00:00
·         wakkadoo-channel/primary                                 | 4.1 kB     00:00
·         wakkadoo-channel                                                            9/9
·         Available Packages
·         ansible.noarch            1.1-0.git201302131322.el6             wakkadoo-channel

6.       Verify you can install then uninstall ansible
·         # yum install -y ansible  (verify successful)

·         # yum remove ansible (verify successful)

Part III: Change All Systems Subscriptions

1.       Login to Satellite WebUI
2.       Click on Systems > Systems Groups
3.       Test small Group of Servers first (Web Servers Group only has 4) and click on Use in SSM


4.       Click on Manage to begin working with Group.

5.       Click on Channels to change the subscription

6.       Check Unsubscribe  for Old-channel channel and Subscribe  for Wakkadoo Channel then click on Alter Subscriptions
·         Click on Change Subscriptions on next page to Confirm.

7.       Verify in the Status that it is in progress, then check for Complete

8.       Once complete, login to one of the systems you selected to work with and verify wakkadoo-channel is subscribed.
·         $ sudo rhn-channel –l

9.       Click on Clear box to unmanage the selected systems.

10.   Repeat the process for all Systems by selecting them all in SSM.

11.   Verify all systems are now Unsubscribed from Old-channel
·         Go to channels > Old-channel > Subscribed Systems
·         If any systems still subscribed, repeat above process.

Part IV: Change Activation Keys
1.       Go to Systems > Activation Keys > WakkadooMaster > Child Channels

2.       Use ctrl key to unselect Old-channel and select Wakkadoo Channel then click on Update Key

3.       Verify you see “Activation key WakkadooMaster has been modified” at the top of screen and the correct keys are listed:
·        

4.       Repeat for MasterKey for now (This key will be removed eventually)

5.       Install new tomcat or base kickstart to test install works for new channel.
·         Verify all config files from PKG1 and packages are installed, ie PKG2, PKG1.

No comments:

Post a Comment