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, check that you have the openSUSE product enabled, and the required channels are fully synchronized.
The products you need for this procedure are:
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 |
-
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_name> \ <child_channel_name_1> \ <child_channel_name_2> \ ... <child_channel_name_n>
Check Synchronization Status
-
In the Uyuni Web UI, navigate to
, then click the channel associated to the repository. -
Navigate to the
Repositories
tab, then clickSync
and checkSync Status
.
-
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 will 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, some operating systems do not trust the GPG key for the Uyuni client tools. The clients can be successfully bootstrapped without the GPG key being trusted. However, you will not be able to install new client tool packages or update them until the keys are trusted.
-
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 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.
-
If you are bootstrapping clients from 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.
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 --with-custom-channels
For more information on registering your clients, see Client Registration Overview.