Registering SL Micro Clients

This section contains information about registering clients running SL Micro operating system x86-64, arm64, and IBM Z (s390x).

The SL Micro 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.

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 SL Micro clients to the SUSE Manager Server, you need to add the required software channels, and synchronize them.

You can add the software channels with the Web UI or from the command line.

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

For the Web UI procedure, you need the following products:

Table 1. SL Micro 6.1 Products - WebUI
OS Version Product Name

SL Micro 6.1 x86-64

SUSE Linux Micro 6.1 x86_64

SL Micro 6.1 arm64

SUSE Linux Micro 6.1 arch64

SL Micro 6.1 s390x

SUSE Linux Micro 6.1 s390x

SL Micro 6.1 ppc64le

SUSE Linux Micro 6.1 ppc64le
Table 2. SL Micro 6.0 Products - WebUI
OS Version Product Name

SL Micro 6.0 x86-64

SUSE Linux Micro 6.0 x86_64

SL Micro 6.0 arm64

SUSE Linux Micro 6.0 arch64

SL Micro 6.0 s390x

SUSE Linux Micro 6.0 s390x
Procedure: Adding Software Channels

  1. In the SUSE Manager Web UI, navigate to Admin  Setup Wizard  Products.

  2. Locate the appropriate products for your client operating system and architecture using the search bar, and check the appropriate product. This will automatically check all mandatory channels. Also all recommended channels are checked as long as the include recommended toggle is turned on. Click the arrow to see the complete list of related products, and ensure that any extra products you require are checked.

  3. Click Add Products and wait until the products have finished synchronizing.

Alternatively, you can add channels from the command prompt. For this procedure, you need the following products:

Table 3. SL Micro 6.1 Products - CLI
OS Version Base Channel

SL Micro 6.1 x86-64

sl-micro-6.1-pool-x86_64
Table 4. SL Micro 6.0 Products - CLI
OS Version Base Channel

SL Micro 6.0 x86-64

sl-micro-6.0-pool-x86_64
Procedure: Adding Software Channels at the Command Prompt

  1. At the command prompt on the SUSE Manager container host, as root, add the appropriate channels:

    mgrctl exec -ti -- mgr-sync add channel <channel_label_1>
mgrctl exec -ti -- mgr-sync add channel <channel_label_2>
mgrctl exec -ti -- mgr-sync add channel <channel_label_n>

  2. Synchronization starts automatically. If you want to synchronize the channels manually, use:

    mgrctl exec -ti -- mgr-sync sync --with-children <channel_name>

  3. Ensure the synchronization is complete before continuing.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress From the Web UI

  1. In the SUSE Manager Web UI, navigate to Admin  Setup Wizard and select the Products tab. This dialog displays a completion bar for each product when they are being synchronized.

  2. Alternatively, you can 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

  1. At the command prompt on the SUSE Manager container host, as root, check the synchronization log file:

    mgrctl exec -ti -- 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.

3. Register Clients

SL Micro clients require a reboot after registering. Although a reboot is automatically scheduled after registration is completed, it is respecting the default reboot manager maintenance window. This window may be several hours after the client is registered. It is advisable to manually reboot the client after the registration script finishes, to speed up the registration and to see the system appear in the system list.

To register your 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 on the container host:

mgrctl exec -ti mgr-create-bootstrap-repo

For more information on registering your clients, see Client Registration.

When using a bootstrap script with SL Micro systems, ensure that the certificate section of the script has this content:

ORG_CA_CERT=RHN-ORG-TRUSTED-SSL-CERT
ORG_CA_CERT_IS_RPM_YN=0

Either edit the bootstrap script directly and add the settings, or create the bootstrap script with these parameters:

mgrctl exec -ti -- mgr-bootstrap --script=bootstrap-sl-micro.sh \
    --ssl-cert=/srv/www/htdocs/pub/RHN-ORG-TRUSTED-SSL-CERT

4. Reboot SL Micro

SL Micro is a transactional system. Transactional updates in general support several reboot methods. It is recommended to use systemd for rebooting in systems managed by SUSE Manager. Using other methods can lead to undesired behavior.

When bootstrapping a transactional system on SUSE Manager, systemd will be configured as the reboot method (REBOOT_METHOD), if the system is in its default configuration. Such a configuration allows SUSE Manager to control the reboot action, and rebooting can be performed immediately or scheduled with SUSE Manager as wanted.

4.1. Background Information

By default, the reboot method during client installation is set to auto. With the auto boot method, rebootmgrd will be used to reboot the system according to the configured policies if the service is running. Policies can be to reboot instantly or during a maintenance window. For more information, see the rebootmgrd(8) man page. Otherwise if rebootmgrd is not running, SUSE Manager will call systemctl reboot.

Using any method different from systemd may cause undesired behavior.