Registering openSUSE Leap 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.

1. Add Software Channels

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

The architectures currently supported are: x86_64 and aarch64. For full list of supported products and architectures, see client-configuration:supported-features.adoc.

In the following section, descriptions often default to the x86_64 architecture. Replace it with other architectures if appropriate.

For example, when working with x86_64 architecture, you need this product:

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

openSUSE Leap 15.1

opensuse_leap15_1

opensuse_leap15_1-uyuni-client

opensuse_leap15_1-updates

opensuse_leap15_1-non-oss

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

opensuse_leap15_2-non-oss-updates

Table 2. OpenSUSE Channels - CLI
OS Version Base Channel Client Channel Updates Channel Non-OSS Channel Non-OSS Updates Channel Backports Updates Channel SLE Updates Channel

openSUSE Leap 15.3

opensuse_leap15_3

opensuse_leap15_3-uyuni-client

opensuse_leap15_3-updates

opensuse_leap15_3-non-oss

opensuse_leap15_2-non-oss-updates

opensuse_leap15_3-backports-updates

opensuse_leap15_3-sle-updates

openSUSE Leap 15.4

opensuse_leap15_4

opensuse_leap15_4-uyuni-client

opensuse_leap15_4-updates

opensuse_leap15_4-non-oss

opensuse_leap15_4-non-oss-updates

opensuse_leap15_4-backports-updates

opensuse_leap15_4-sle-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 \
    <base_channel_label>
    <child_channel_label_1> \
    <child_channel_label_2> \
    ... <child_channel_label_n>
  2. If automatic synchronization is turned off, synchronize the channels:

    spacewalk-repo-sync -p <base_channel_label>
  3. Ensure the synchronization is complete before continuing.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress from the Web UI
  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.

3. Manage GPG Keys

Clients use GPG keys to check the authenticity of software packages before they are installed. Only trusted software can be installed on clients.

Trusting a GPG key is important for security on clients. It is the task of the administrator to decide which keys are needed and can be trusted. Because a software channel cannot be used when the GPG key is not trusted, the decision of assigning a channel to a client depends on the decision of trusting the key.

For more information about GPG keys, see client-configuration:gpg-keys.adoc.

4. 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.