Registering openSUSE Clients

This section contains information about registering Salt clients running openSUSE operating systems. Uyuni supports openSUSE Leap 15 clients using Salt. Traditional clients are not supported.

Bootstrapping is supported for starting openSUSE clients and performing initial state runs such as setting repositories and performing profile updates.

Add Software Channels

Before you register openSUSE clients to your Uyuni Server, you need to add the required software channels, and synchronize them.

The products you need for this procedure are:

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

openSUSE Leap 15.1

opensuse_leap15_1

opensuse_leap15_1-uyuni-client

opensuse_leap15_1-updates

opensuse_leap15_1-non-oss and opensuse_leap15_1-non-oss-updates

openSUSE Leap 15.2

opensuse_leap15_2

opensuse_leap15_2-uyuni-client

opensuse_leap15_2-updates

opensuse_leap15_2-non-oss and opensuse_leap15_2-non-oss-updates

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 \
    <channel_label_1> \
    <channel_label_2> \
    <channel_label_3> \
    ... <channel_label_n>
  2. Synchronize the channels:

    spacewalk-repo-sync
  3. Ensure the synchronization is complete before continuing.

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 need to check all the base and child channel log files to be sure that the synchronization is complete.

openSUSE channels can be very large. Synchronization can sometimes take several hours.

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.

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 channel assigned 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:

    uyuni-gpg-pubkey-0d20833e.key

    You do not need to delete any previously stored keys.

  3. If you are bootstrapping clients from the Uyuni Web UI, you 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

To register your openSUSE clients, you need a bootstrap repository. By default, bootstrap repositories are automatically created, and regenerated daily for all synchronized products. You can manually create the bootstrap repository from the command prompt, using this command:

mgr-create-bootstrap-repo

For more information on registering your clients, see client-configuration:registration-overview.adoc.