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.
Bootstrapping can be used with Debian clients for performing initial state runs, and for profile updates.
Some preparation is required before you can register Debian clients to the Uyuni Server.
If you are using Debian 9, install the
apt-transport-https package on the client before you attempt to register.
On the client, at the command prompt, as root, run:
apt install apt-transport-https
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 correctly with the Uyuni server before registration.
The Uyuni Server requires the
On the Uyuni Server, at the command prompt, as root, run:
zypper in spacewalk-utils
At the command prompt on the Uyuni Server, as root, install the
zypper in spacewalk-utils
Add the Debian channels. For Debian 9:
spacewalk-common-channels -u admin -a amd64-deb debian-9-pool-amd64-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-9-amd64-main-security-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-9-amd64-main-updates-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-9-amd64-uyuni-client
For Debian 10:
spacewalk-common-channels -u admin -a amd64-deb debian-10-pool-amd64-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-10-amd64-main-security-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-10-amd64-main-updates-uyuni spacewalk-common-channels -u admin -a amd64-deb debian-10-amd64-uyuni-client
In the Uyuni Web UI, navigate to, and check every Debian channel.
Repositoriestab, navigate to the
Syncsubtab, and click Sync Now. You can also create a regular synchronization schedule on this page.
Debian channels can be very large. Synchronization can sometimes take several hours.
There are two ways to check if a channel has finished synchronizing:
In the Uyuni Web UI, navigate to, and click the channel associated to the repository. Navigate to the tab, and check
Check the synchronization log file at the command prompt with
tail -f /var/log/rhn/reposync/channel-label.log. Each child channel will generate 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.
By default, Debian does not trust the GPG key for Uyuni Debian client tools.
The clients can be successfully bootstrapped without the GPG key being trusted. However, they will not be able to install new client tool packages or update them.
To fix this, add the key to the
ORG_GPG_KEY= parameter in all Debian bootstrap scripts:
You do not need to delete any previously stored keys.
If you are bootstrapping clients using 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.
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:
For Debian 10, select
debian10-amd64-uyuni when prompted.
For more information on registering your clients, see client-configuration:registration-overview.adoc.