Registering Oracle Linux Clients

This section contains information about registering traditional and Salt clients running Oracle Linux operating systems.

Traditional clients are not available on Oracle Linux 8. Oracle Linux 8 clients are only supported as Salt clients.

Add Software Channels

Before you register Oracle Linux clients to your Uyuni Server, check that you have the Oracle Linux product enabled, and the required channels are fully synchronized.

The channels you need for this procedure are:

Table 1. Oracle Channels - CLI
OS Version Base Channel Client Channel Updates Channel

Oracle Linux 6




Oracle Linux 7




Oracle Linux 8




Procedure: Adding Software Channels at the Command Prompt
  1. At the command prompt on the Uyuni Server, as root, use the spacewalk-common-channels command to add the appropriate channels:

    spacewalk-common-channels \
    <base_channel_name> \
    <child_channel_name_1> \
    <child_channel_name_2> \
    ... <child_channel_name_n>

The client tools channel provided by spacewalk-common-channels is sourced from Uyuni and not from SUSE.

For Oracle Linux 8 clients, add both the Base and Appstream channels. You will require packages from both channels. If you do not add both channels, you will not be able to create the bootstrap repository, due to missing packages.

Check Synchronization Status

Procedure: Checking Synchronization Progress
  1. In the Uyuni Web UI, navigate to Software  Manage  Channels, then click the channel associated to the repository.

  2. Navigate to the Repositories tab, then click Sync and check Sync Status.

Procedure: Checking Synchronization Progress from the Command Prompt
  1. At the command prompt on the Uyuni Server, as root, use the tail command to check the synchronization log file:

    tail -f /var/log/rhn/reposync/<channel-label>.log
  2. Each child channel generates its own log during the synchronization progress. You will need to check all the base and child channel log files to be sure that the synchronization is complete.

Create an Activation Key

You will need to create an activation key that is associated with your Oracle Linux channels.

For more information on activation keys, see Activation Keys.

Trust GPG Keys on Clients

By default, some operating systems do not trust the GPG key for the Uyuni client tools. The clients can be successfully bootstrapped without the GPG key being trusted. However, you will not be able to install new client tool packages or update them until the keys are trusted.

Procedure: Trusting GPG Keys on Clients
  1. On the Uyuni Server, at the command prompt, check the contents of the /srv/www/htdocs/pub/ directory. This directory contains all available public keys. Take a note of the key that applies to the client you are registering.

  2. Open the relevant bootstrap script, locate the ORG_GPG_KEY= parameter and add the required key. For example:


    You do not need to delete any previously stored keys.

  3. If you are bootstrapping clients from the Uyuni Web UI, you will need to use a Salt state to trust the key. Create the Salt state and assign it to the organization. You can then use an activation key and configuration channels to deploy the key to the clients.

Register Clients

Oracle Linux clients are registered in the same way as all other clients. For more information, see Client Registration Overview.

To register and use Oracle Linux 6 clients, you need to configure the Uyuni Server to support older types of SSL encryption. For more information about how to resolve this error, see Registering Older Clients at Troubleshooting Clients.