5.2. Updating a Self-Registered Satellite

A self-registered Red Hat Satellite server is registered to itself rather than directly to the Red Hat Customer Portal. A self-registered Satellite server is able to synchronize with the Red Hat Customer Portal then apply updates to itself at the same time as providing other required updates.

Procedure 5.2. To Update a Self-Registered Satellite:

  1. It is essential to make a full backup of a self-registered Satellite server prior to doing an upgrade as package updates cannot be tested. For instructions on how to backup and, if necessary, restore a Satellite server see Backup and Disaster Recovery in the Red Hat Satellite 6.1 User Guide.
    1. Ensure your backup location has enough disk space to contain a copy of all of the following directories:
      • /etc/
      • /var/lib/pulp
      • /var/lib/mongodb
      • /var/lib/pgsql/
      This can be a considerable amount of space so plan accordingly.
    2. Stop all services:
      # katello-service stop
    3. Run the backup script:
      # /usr/bin/katello-backup backup_directory
      This process can take a long time to complete, due to the amount of data to copy.
    4. Restart all services:
      # katello-service start
  2. Synchronize to Satellite server:
    1. Navigate to ContentSync Status. Based on the subscriptions and repositories enabled, the list of product repositories available for synchronization is displayed.
    2. Click the arrow next to the product name to see available content.
    3. Select the content you want to synchronize.
    4. Click Synchronize Now to starting synchronizing. The status of the synchronization process will appear in the Result column. If synchronization is successful, Sync complete will appear in the Result column. If synchronization failed, Error syncing will appear.

    Note

    Content synchronization can take a long time, and depends on the speed of disk drives, network connection speed, and the amount of content selected for synchronization.
  3. Optionally, publish and promote the required content views:
    1. After a content view has been created, it needs to be published in order for it to be visible and usable by hosts. Before publishing the content view definition, make sure that the content view definition has the necessary products, repositories and filters.
      To publish the content view:
      1. Click ContentContent Views.
      2. Click on the content view that represents the Satellite server.
      3. Click Publish New Version.
      4. Fill in a comment.
      5. Click Save.
    2. After the content view has been published it needs to promoted into the required life cycle environment.
      To promote the content view:
      1. On the main menu, click ContentContent Views.
      2. In the Name column, select the content view that represents the Satellite server.
      3. On the Versions tab, identify the latest version, and click Promote.
      4. Identify the promotion path where you want to promote the content view, select the appropriate life cycle environment, and click Promote Version.
      5. After the promotion has completed, the Versions tab updates to display the new status of your content views.
  4. Update the Satellite server:
    # yum update
    # katello-installer --upgrade
  5. Restart the services:
    # katello-service restart