Chapter 3. Transitioning from Satellite 5 to 6

1. Ensure you are in the root directory:

   # cd

   Copy to Clipboard Toggle word wrap

2. Download the script:

   # curl -O http://satellite.example.com/pub/bootstrap.pycurl -O http://satellite.example.com/pub/bootstrap.pycurl -O http://satellite.example.com/pub/bootstrap.py

   Copy to Clipboard Toggle word wrap

   This will install the script to the current directory.

3. Make the script executable:

   # chmod +x bootstrap.py

   Copy to Clipboard Toggle word wrap

4. To confirm that the script can now be run, view the usage statement as follows:

   # ./bootstrap.py -h

   Copy to Clipboard Toggle word wrap

5. Optionally, when the transition process is complete, remove the script:

   # cd
   # rm bootstrap.py

   Copy to Clipboard Toggle word wrap

Migrating a Red Hat Enterprise Linux 6 System

1. Enter the bootstrap command as follows with values suitable for your environment.

   For the --server option, specify the FQDN name of Satellite Server or Capsule Server. For --location, --organization, and --hostgroup options, use quoted names, not labels, as arguments to the options.

   # bootstrap.py --login=admin \
   --server satellite6.example.com \
   --location="Example Location" \
   --organization="Example Organization" \
   --hostgroup="Example Host Group" \
   --activationkey=activation_key

   Copy to Clipboard Toggle word wrap

   The script will prompt you for the password corresponding to the Satellite user name you entered with the --login option.

2. The script will run and send notices of progress to stdout. Watch for output prompting you to approve the Puppet certificate. For example:

   [NOTIFICATION], [2016-04-26 10:16:00], [Visit the UI and approve this certificate via Infrastructure->Capsules]
   [NOTIFICATION], [2016-04-26 10:16:00], [if auto-signing is disabled]
   [RUNNING], [2016-04-26 10:16:00], [/usr/bin/puppet agent --test --noop --tags no_such_tag --waitforcert 10]

   Copy to Clipboard Toggle word wrap

3. The client will wait until an administrator approves the Puppet certificate. Sign the Puppet certificate as follows:

   1. In the web UI, navigate to Infrastructure > Capsules.
   2. Select Certificates to the right of the name of the Capsule corresponding to the FQDN given with the --server option.
   3. In the Actions column select Sign to approve the client’s Puppet certificate.
   4. Return to the client to see the remainder of the bootstrap process completing.
4. In the web UI, navigate to Hosts > All hosts and ensure that the client is connected to the correct host group.

1. Configure new subscriptions:

   1. Log in to the Customer Portal and go to SUBSCRIPTIONS.
   2. Navigate to Inventory and click Satellite Organizations.
   3. Select the check box to the left of the name of the old Satellite 5 Server and click Delete Selected. In the alert box that appears, click Delete to delete the unit.
   4. Click on the name of the new Satellite 6 Server and select the check box to the left of the name of the transition subscription. Click Remove selected. In the alert box click Remove to remove the subscription.
   5. Click Attach a subscription, select the real Satellite subscription, and click Attach selected.

   6. Run the following command on the new Satellite 6 Server to refresh subscription manager.

      # subscription-manager refresh

      Copy to Clipboard Toggle word wrap

2. Enable repositories on the new Satellite 6 Server

   1. On the old Satellite 5 Server use the following command to view what channels you had enabled.

      # spacewalk-channel -l

      Copy to Clipboard Toggle word wrap

   2. On the new Satellite 6 Server use the following command to list enabled repositories for an organization:

      # hammer product list --organization "organization_name"

      Copy to Clipboard Toggle word wrap

   3. Configure the new Satellite 6 Server to ensure all necessary repositories are enabled.

      For Web UI users

      Navigate to Content Red Hat Repositories and select repositories to be enabled.

      For CLI Users

      Enable repositories using either the name or ID number. Optionally, include the release version and base architecture.

      # hammer repository-set enable \
      --product "product_name" \
      --name "repository_name" \
      --organization "org_name" \
      --releasever "" \
      --basearch "x86_64"

      Copy to Clipboard Toggle word wrap