Registering Debian Clients

This section contains information about registering Salt clients running Debian operating systems.

SUSE does not provide support for Debian operating systems. Uyuni allows you to manage Debian clients, but support is not provided. Using Uyuni to manage Debian clients is experimental. These instructions have been tested on Debian 9 Stretch and Debian 10 Buster. Do not rely on Debian clients in a production environment.

Debian is supported for Salt clients only. Traditional clients are not supported.

Bootstrapping can be used with Debian clients for performing initial state runs, and for profile updates.

Prepare to Register

Some preparation is required before you can register Debian clients to the Uyuni Server:

  • If you are using Debian 9, install the required packages on the client before you attempt to register. On the client, at the command prompt, as root, run:

    apt install apt-transport-https python-apt python3-apt
  • Ensure DNS is correctly configured and provides an entry for the client. Alternatively, you can configure the /etc/hosts files on both the Uyuni Server and the client with the appropriate entries.

  • The client must have the date and time synchronized with the Uyuni Server before registration.

Add Software Channels

Before you can register Debian 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. Debian Channels - CLI
OS Version Base Channel Client Channel Updates Channel Security Channel

Debian 9

debian-9-pool-amd64-uyuni

debian-9-amd64-uyuni-client

debian-9-amd64-main-updates-uyuni

debian-9-amd64-main-security-uyuni

Debian 10

debian-10-pool-amd64-uyuni

debian-10-amd64-uyuni-client

debian-10-amd64-main-updates-uyuni

debian-10-amd64-main-security-uyuni

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.

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

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

Debian clients can require multiple GPG keys to be installed.

Register Clients

To register your Debian clients, you need a bootstrap repository. By default, bootstrap repositories are regenerated daily. You can manually create the bootstrap repository from the command prompt, using this command:

mgr-create-bootstrap-repo

For Debian 10, select debian10-amd64-uyuni when prompted.

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