Registering openSUSE MicroOS Clients

Table of Contents

1. Add Software Channels
2. Check Synchronization Status
3. Trust Certificates Keys on Clients
4. Register Clients

This section contains information about registering clients running these openSUSE MicroOS operating systems:

openSUSE MicroOS

Support for openSUSE MicroOS clients is provided as a technology preview for testing purposes, and not all features are fully functional at this stage. This feature is expected to be fully supported in a later version of Uyuni. Do not use this feature on production systems.

The MicroOS uses transactional updates. Transactional updates are atomic (all updates are applied only if all updates succeed) and support rollbacks. They do not affect a running system as no changes are activated until after the system is rebooted. This information is displayed in the Systems Details Overview subtab.

For more information on transactional updates and rebooting, see https://documentation.suse.com/sles/html/SLES-all/cha-transactional-updates.html.

1. Add Software Channels

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

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

The channels you need for this procedure are:

Table 1. openSUSE MicroOS Channels - CLI
OS Version	Base Channel	Client Channel	Updates Channel
openSUSE MicroOS	opensuse_tumbleweed	opensuse_tumbleweed-non-oss	opensuse_tumbleweed-update

Procedure: Adding Software Channels at the Command Prompt

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>

If automatic synchronization is turned off, synchronize the channels:
```
spacewalk-repo-sync -p <base_channel_label>
```
Ensure the synchronization is complete before continuing.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress from the Web UI

In the Uyuni Web UI, navigate to Software Manage Channels, then click the channel associated to the repository.
Navigate to the Repositories tab, then click Sync and check Sync Status.

Procedure: Checking Synchronization Progress from the Command Prompt

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

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

3. Trust Certificates Keys on Clients

openSUSE MicroOS is not yet fully enabled, so there are some manual steps to trust the Uyuni SSL certificate on MicroOS clients.

Procedure: Installing and Configuring Salt

On the client, at the command prompt, as root, retrieve the SSL certificate file from the server:

curl -k https://uyuni-server.hispa-net.com/pub/RHN-ORG-TRUSTED-SSL-CERT -o /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT

Update the certificates on the client:
```
update-ca-certificates
```

Install the required packages:

transactional-update pkg install salt-minion dmidecode

Reboot the client. If a message is shown indicating that there is a conflict with busybox-hostname, click Deinstallation of busybox-hostname.
Create a new file called /etc/salt/minion.d/susemanager-transactional.conf with this content:
```
module_executors:
- transactional_update
- direct_call
```

Your Uyuni Server will not show the true state of the client in the Web UI until after you have rebooted the client. This feature is expected to be fully supported in a later version of Uyuni.

If Salt is failing to install any software, you could be using an old version of Salt. Upgrade your Salt packages to the latest version to resolve this problem.

4. Register Clients

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