Registering Oracle Linux Clients

Table of Contents

Add Software Channels
Check Synchronization Status
Create an Activation Key
Trust GPG Keys on Clients
Register 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, you need to add the required software channels, and synchronize them.

The channels you need for this procedure are:

Table 1. Oracle Channels - CLI
OS Version	Base Channel	Client Channel	Updates Channel
Oracle Linux 6	oraclelinux6	oraclelinux6-uyuni-client	-
Oracle Linux 7	oraclelinux7	oraclelinux7-uyuni-client	-
Oracle Linux 8	oraclelinux8	oraclelinux8-uyuni-client	oraclelinux8-appstream

Oracle Linux 6 is now at end-of-life, and the ISO images provided in the repository are out of date. Bootstrapping new Oracle Linux 6 clients using these packages will fail. If you need to bootstrap new Oracle Linux 6 clients, follow the troubleshooting procedure in client-configuration:tshoot-clients.adoc.

Procedure: Adding Software Channels at the Command Prompt

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_label>
<child_channel_label_1> \
<child_channel_label_2> \
... <child_channel_label_n>

Synchronize the channels:

spacewalk-repo-sync -p <base_channel_label>

Ensure the synchronization is complete before continuing.

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 require packages from both channels. If you do not add both channels, you cannot create the bootstrap repository, due to missing packages.

If you are using modular channels, you must enable the Python 3.6 module stream on the client. If you do not provide Python 3.6, the installation of the spacecmd package will fail.

The AppStream repository provides modular packages. This results in the Uyuni Web UI showing incorrect package information. You cannot perform package operations such as installing or upgrading directly from modular repositories using the Web UI or API.

You can use the AppStream filter with content lifecycle management (CLM) to transform modular repositories into regular repositories. Make sure to include python:3.6 using an AppStream filter if you want to use spacecmd on the clients.

Alternatively, you can use Salt states to manage modular packages on Salt clients, or use the dnf command on the client. For more information about CLM, see administration:content-lifecycle.adoc.

Check Synchronization Status

Procedure: Checking Synchronization Progress

In the Uyuni Web UI, navigate to Software Manage Channels, then click the channel associated to the repository.
Navigate to the Repositories tab, then click Sync and check Sync Status.

Procedure: Checking Synchronization Progress from the Command Prompt

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
```
Each child channel generates its own log during the synchronization progress. You need to check all the base and child channel log files to be sure that the synchronization is complete.

Create an Activation Key

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

For more information on activation keys, see client-configuration:activation-keys.adoc.

Trust GPG Keys on Clients

By default, operating systems trust only their own GPG keys when they are installed, and do not trust keys provided by third party packages. The clients can be successfully bootstrapped without the GPG key being trusted. However, you cannot install new client tool packages or update them until the keys are trusted.

Salt clients are set to trust SUSE tools channels GPG keys when they are bootstrapped. For all other clients and channels, you need to manually trust third party GPG keys.

If you are bootstrapping Salt clients from the Uyuni Web UI, you can use a Salt state to trust the key. For more information on custom Salt states, see salt:custom-states.adoc.

Procedure: Trusting GPG Keys on Clients

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 channel assigned to the client you are registering.
Open the relevant bootstrap script, locate the ORG_GPG_KEY= parameter and add the required key. For example:
```
uyuni-gpg-pubkey-0d20833e.key
```
You do not need to delete any previously stored keys.

Register Clients

Oracle Linux clients are registered in the same way as all other clients. For more information, see client-configuration:registration-overview.adoc.

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 client-configuration:tshoot-clients.adoc.