Registering AlmaLinux Clients

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

Traditional clients are not available on AlmaLinux 8. AlmaLinux 8 clients are only supported as Salt clients.

Registering AlmaLinux clients to SUSE Manager is tested with the default SELinux configuration of enforcing with a targeted policy. You do not need to disable SELinux to register AlmaLinux clients to SUSE Manager.

1. Add Software Channels

Before you can register AlmaLinux clients to your SUSE Manager Server, you need to add the required software channels, and synchronize them.

The architectures currently supported are: x86_64 and aarch64. For full list of supported products and architectures, see client-configuration:supported-features.adoc.

For example, when working with x86_64 architecture, you need this product:

Table 1. CentOS Products - WebUI
OS Version Product Name

AlmaLinux 8

AlmaLinux 8 x86_64

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 required channels. 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 at the command prompt. The channels you need for this procedure are:

Table 2. CentOS Channels - CLI
OS Version Base Channel

AlmaLinux 8

almalinux8-x86_64

Procedure: Adding Software Channels at the Command Prompt
  1. At the command prompt on the SUSE Manager Server, as root, use the mgr-sync command to add the appropriate channels:

    mgr-sync add channel <channel_label_1>
    mgr-sync add channel <channel_label_2>
    mgr-sync add channel <channel_label_n>
  2. Synchronization starts automatically. If you want to synchronize the channels manually, use:

    mgr-sync sync --with-children <channel_name>
  3. Ensure the synchronization is complete before continuing.

If you are using modular channels, you must enable the Python 3.6 module stream on the client. If you do not provide Python 3.6, the installation of the spacecmd package will fail.

You might notice some disparity in the number of packages available in the AppStream channel between upstream and the SUSE Manager channel. You might also see different numbers if you compare the same channel added at a different point in time. This is due to the way that AlmaLinux manages their repositories. AlmaLinux removes older version of packages when a new version is released, while SUSE Manager keeps all of them, regardless of age.

The AppStream repository provides modular packages. This results in the SUSE Manager Web UI showing incorrect package information. You cannot perform package operations such as installing or upgrading directly from modular repositories using the Web UI or API.

You can use the AppStream filter with content lifecycle management (CLM) to transform modular repositories into regular repositories. Make sure to include python:3.6 using an AppStream filter if you want to use spacecmd on the clients.

Alternatively, you can use Salt states to manage modular packages on Salt clients, or use the dnf command on the client. For more information about CLM, see administration:content-lifecycle.adoc.

2. Check Synchronization Status

Procedure: Checking Synchronization Progress
  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 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.

3. Create an Activation Key

You need to create an activation key that is associated with your AlmaLinux channels.

For more information on activation keys, see client-configuration:activation-keys.adoc.

4. Register Clients

AlmaLinux clients are registered in the same way as all other clients. For more information, see client-configuration:registration-overview.adoc.

5. Manage Errata

When you update AlmaLinux clients, the packages include metadata about the updates.