Release notes for Uyuni Server

With Uyuni 2026.08, we are archiving the release notes of Uyuni versions older than 2025.05 to make the document smaller and easier to navigate.

Release notes for older versions, from 2021.12 up to 2024.12, can still be found at the website.

Uyuni 2026.08 expands its list of supported operating systems with full management support for Ubuntu 26.04 LTS clients. With this update, administrators can manage Ubuntu 26.04 LTS systems directly from Uyuni 2026.08, ensuring compliance, security, and consistency across all managed systems.

For detailed instructions on registering and managing Ubuntu clients, refer to the client registration and supported features sections in the documentation.

openSUSE Leap 15.6 reached end of life on April 30, 2026.

The Uyuni client tools supporting openSUSE Leap 15.X have been used also for openSUSE Leap Micro 5.X and, in an upcomig Uyuni release the support for those client tools will be removed.

This update addresses important security vulnerabilities. We recommend upgrading your Uyuni instances as soon as possible.

With 2026.06, as openSUSE Leap 15.6 was out of support for already some time, the base OS that is now used to build our containers is openSUSE Leap 16.0.

openSUSE Leap 16.0 uses Python 3.13 by default. This Python version (and probably other SSL clients) validates certificates strictly and rejects any CA certificate that does not mark the X509v3 Basic Constraints extension as critical.

Please refer to the Migrate SSL Certificate Authorities for detailed instructions to migrate the SSL Certificate Authorities.

In addition, the bump of the container base to Leap 16.0 will trigger a PostgreSQL reindexing, and this could take a long time. This is due to the glibc upgrade from Leap 15.6 (glibc 2.38) to Leap 16.0 (glibc 2.40).

openSUSE Tumbleweed will soon receive an update to Podman 6.0.0. Please be aware that this major release introduces a significant number of breaking changes. While the required database migration to SQLite is handled automatically by Podman in the background, we strongly urge all administrators to review the upstream documentation to understand how these changes might impact their specific setups. Users running Uyuni Server or Proxies on other operating systems should also prepare for these updates as Podman 6.0.0 eventually lands in their distribution’s repositories.

For a complete list of breaking changes and technical details, please read the official Podman 6.0.0 Release Notes.

Uyuni 2026.06 now supports in-place product migration of managed clients from SUSE Linux Enterprise Server 15 SP7 to SUSE Linux Enterprise Server 16.0. Administrators can perform the migration directly from the Uyuni web interface or through the API.

For more information, see the SUSE Linux Enterprise Server 16 Upgrade Guide.

Uyuni 2026.06 can now be deployed on a FIPS-enabled host OS.

This allows organizations with strict cryptographic compliance requirements to run Uyuni within a FIPS-enforced environment.

Uyuni 2026.06 adds bootstrap repository definitions and product entries for SUSE Liberty Linux 9.6 EMS (Extended Minor Version Support).

Administrators can now register and manage SUSE Liberty Linux 9.6 clients directly from Uyuni.

This update addresses security vulnerabilities. We recommend upgrading your Uyuni instances as soon as possible.

Debian 12 (Bookworm) reaches end of life on June 30, 2026.

Uyuni will continue to support the management of Debian 12 clients for a three-month grace period, until September 30, 2026.

The domain registry-store.suse.com was a temporary name used during the migration of the SUSE registry infrastructure. The current and permanent domain is registry-storage.suse.com.

Uyuni introduces support for managing Red Hat Enterprise Linux 10 and its compatible distributions, including SUSE Liberty Linux 10, AlmaLinux 10, Oracle Linux 10 and Rocky Linux 10. This enables organizations running mixed enterprise Linux environments to manage all their systems through a single, unified platform using consistent tools and workflows.

Uyuni introduces online database backup management via mgradm, based on postgresql continuous archiving (Write-Ahead Logging).

Administrators can manage the full backup lifecycle directly from the command line, including creating base backups, monitoring backup status, rebasing, restoring database content, and disabling backup management when needed.

Backups are stored in a dedicated Podman volume and are designed to reduce the risk of data loss by continuously archiving database changes.

For more information, refer to the Database Backup Management section in the documentation.

Uyuni introduces a modernized approach to SCAP (Security Content Automation Protocol) auditing. The enhanced SCAP integration streamlines compliance scanning by centralizing content management, introducing reusable policies, supporting automated remediation, and eliminating the need to pre-stage SCAP files on managed systems.

Key improvements include centralized SCAP content management, reusable scan policies, automated remediation support, and recurring scan scheduling.

This feature is available as a Technology Preview and will be moved to a fully supported state in a future release.

Uyuni supports migrating managed clients from SUSE Linux Enterprise Server 15 SP7 to SUSE Linux Enterprise Server 16.0 using the built-in product migration feature. This enables administrators to seamlessly upgrade their managed systems to the latest SUSE Linux Enterprise Server release directly from the Uyuni web interface.

Uyuni introduces a new reporting dashboard integrated with the existing Grafana monitoring stack.

While the read-only reporting database continues to support third-party visualization tools such as Metabase, this new dashboard provides a convenient out-of-the-box option for viewing and filtering report data. Administrators can leverage Grafana’s powerful visualization and filtering capabilities directly within the existing monitoring infrastructure, eliminating the need to configure additional tools.

Since the start of containerization, installation and configuration scripts were part of our uyuni-tool’s mgradm utility. This release changes that and all installation and upgrade scripts for both database and server are now part of the images themselves. This concerns only scripts for actual server and database. Other scripts and responsibilities, such as creating systemd entries, self-signed certificates and major db upgrades, are still done by the mgradm tool.

This change allows for Podman and Kubernetes versions to have identical configurations and opens further possibilities in the future.

The new listMigrationTargetsWithChannels endpoint returns, for each migration target, the standard base channel label and childs channels.

This allows API consumers to select the correct target base channel for use with scheduleProductMigration in a single call.

Grafana has been updated from version 11.6.11 to version 11.6.14+security-01

Check the upstream changelog for all the details.

For detailed information about the fixes and features, you can refer to the following links:

This update addresses several high-severity CVEs. We highly recommend upgrading your Uyuni instances as soon as possible to ensure they remain secure. The following CVEs are included in this release:

Updated schema to improve performance. Changes made will remove existing OVAL data upon migration. OVAL data will be resynced within the next 24h. If immediate use of the feature is desired a manual oval-data-sync should be performed.

This release update Tomcat to version 11 and Hibernate to version 7. Together with this a lot of Java packages were updated as well. This renewal of the codebase was required due to EOL of the currently used versions.

Grafana has been updated from version 11.5.10 to version 11.6.11

Check the upstream changelog for all the details.

For detailed information about the fixes and features, you can refer to the following links:

Uyuni also introduces support for managing openSUSE Leap 16.0 systems. This enables administrators and developers to manage community-driven environments using the same tools and workflows as enterprise platforms, making openSUSE Leap 16.0 well suited for development, testing, and mixed environments.

For detailed instructions on registering and managing these clients, refer to the Registration section in the documentation.

Uyuni introduces the ability to edit Ansible playbook variables directly in the Web UI. This feature allows a single playbook to be executed dynamically across multiple systems by customizing variable values at runtime, eliminating the need to modify the source playbook.

The Web UI now generates input fields based on the variables defined in a playbook. When selecting a playbook under System > Ansible > Playbooks, administrators can provide system-specific values immediately before execution, making it easier to reuse playbooks for different configurations.

Administrators can now manage Role-Based Access Control (RBAC) directly through the Web UI. Previously, these tasks required direct API interaction.

This enhancement simplifies the management of User Access Groups and policies, providing an intuitive interface to utilize the fine-grained access control features introduced in Uyuni 2026.01.

Prometheus golang-github-prometheus-prometheus has been upgraded from version version 2.53.4 to next LTS version 3.5.0. The update includes number of enhancements and bug fixes.

Check the upstream changelogs for more details:

Uyuni introduces support for containerized deployments of BIND and DHCP services on branch servers.

By default, these formulas pull container images from registry.suse.com.

With this Uyuni release we update the database container to support PostgreSQL 18. This also means that an upgrade will trigger a database migration.

Starting with Uyuni 2026.01, mgradm migrate subcommand has been deprecated. The migrate command is not needed for Uyuni as it uses a rolling release model.

Ubuntu 20.04 was End of Life on May 31st, 2025.

After a grace period of more than 3 months, Uyuni will stop support for this operating system after Uyuni 2026.01.

While existing client tools repositories will not be removed, they will not get updates.

As for the code, it will not be broken on purpose, but it will not get tested for Ubuntu 20.04 anymore.

All remaining users with Ubuntu 20.04 systems are encouraged to migrate to Ubuntu 22.04 or Ubuntu 24.04 as soon as possible.

This release addresses a few high-severity CVEs. These vulnerabilities could pose significant security risks if not addressed.

Considering that the affected one was only legacy code not used anymore in Uyuni, from the server-image it was decided to remove susemanager-tftpsync, and from the proxy-httpd-image the removed package was susemanager-tftpsync-recv.

In addition, another security issue worth mentioning:

With 2025.10, as previously decided by the community, and as openSUSE Leap Micro 5.5 was out of support for already some time, the base OS that is now validated is openSUSE Tumbleweed. Of course, this does not mean that any Community member is forced to run Uyuni on this OS, rather only that this is the version that was internally tested. We would be glad to hear feedback from the Community using a different host OS, and will try our best to fix any issue showing up on any other version.

To perform the migration from openSUSE Leap Micro 5.5, please check the Migrate Uyuni Server from openSUSE Leap Micro 5.5 to Tumbleweed section of the documentation.

Uyuni 2025.10 now supports managing openSUSE Tumbleweed as client.

For details on the registration process, please refer to the Registration section. To learn more about supported features, consult the Supported Features section in our documentation.

It is now possible to schedule product migrations directly from the web UI for multiple servers at once using the System Set Manager. This streamlines large-scale migrations by allowing administrators to plan and execute them in a single step.

This new feature allows administrators to generate a support data archive for a system directly from the web UI and upload it to SUSE Customer Center. This simplifies the process of providing support information for troubleshooting.

Uyuni 2025.10 introduces a container-based KIWI image build system, in addition to the existing legacy KIWI and KIWI NG tools.

The build system used depends on the underlying OS or specific pillar values:

Administrators can override the default behavior using the following pillar or custom values:

This release also allows all SUSE family OSes to become build hosts, that means openSUSE Leap and openSUSE Tumbleweed as well. Those will automatically use containerized KIWI.

The images POS_Image-RPi-Bootstrap and pxe-yomi-image-opensuse15 were not really in use, and as they were having build failures and no reports had ever been received about them, it was simply decided to drop them.

Due to the changes introduced in this version, the Uyuni Documentation API has been upgraded from version 28 to 29.

For the XMLRPC API, some standard exceptions are now FaultException, and some were renamed:

These can be considered breaking changes as when some of these exceptions are expected to be caught, different ones are now received instead, and the handling will not work anymore.

For Rest-like-API it might not be considered a breaking change, as there are no exceptions but error codes.

For further details about the API, please refer to the Uyuni API Documentation.

This update includes some critical fixes for Salt. The following CVE fixes are part of this release:

This update includes some critical fixes for Uyuni Server. The following CVE fixes are part of this release:

Uyuni 2025.05 now includes the PostgreSQL database in a separate container. As this new database container no longer shares the SSL certificate with the web server, the password of the SSL CA key is required when upgrading from any older version. When using third party certificates, a certificate and key for the database will need to be provided instead.

To help with backing up and restoring the data a new tool mgradm backup command is available, more information about it can be found in the Backup and restore section of the documentation.

Please check the list of containers for further reference.

Uyuni 2025.05 now supports Role-Based Access Control (RBAC) to provide users with fine-grained access control and configuration options. This enhancement centralizes access control rules, making them easier to manage and adapt. The implementation is designed to be flexible, allowing new use cases and rules to be defined through configuration rather than code changes. The Uyuni Server will include sensible default policies while also enabling users to create custom access policies (user access groups) to suit their specific requirements.

The Uyuni Server has this feature enabled by default, and includes sensible default policies while also enabling users to create custom access policies (user access groups) to suit their specific requirements.

Uyuni 2025.05 introduces a new online synchronization mechanism between the Hub and peripheral servers, providing a more user-friendly and automated approach to content synchronization. This enhancement leverages existing stable mechanisms to deliver a robust and efficient solution and significantly improves both performance and the overall user experience. With the Hub architecture, centralized content management is now seamlessly extended to peripheral servers.

The new 'Hub online synchronization' feature builds on the existing repository synchronization mechanism. It allows peripheral servers to sync their software channels directly from repositories hosted on the Hub server. Once the connection is established, the Hub becomes the primary content source for its connected peripheral servers.

Currently, this functionality is limited to software channels, but future releases will expand support to include other artifacts such as images and configuration channels.

As part of this improvement, the already deprecated ISSv1 will be removed. ISSv2 will remain available for offline synchronization scenarios.

Uyuni 2025.05 includes a range of enhancements to its Ansible integration, making it easier to manage automation workflows directly from within the product. These improvements aim to streamline day-to-day operations and increase visibility and control over Ansible-driven configurations.

Key improvements include:

These enhancements mark a major step forward in improving Ansible usability and integration in Uyuni.

Uyuni 2025.05 introduces a built-in backup and restore solution via the mgradm backup command-line tool. It provides a reliable and consistent way to safeguard your Uyuni installation, simplifying disaster recovery and system migration.

The mgradm backup create command performs a full backup of all critical data, while mgradm backup restore enables system recovery. Additional subcommands and options are available and can be viewed using the tool’s help output.

Regular use of this tool is recommended to prevent data loss and ensure quick recovery in case of failure.

Uyuni 2025.05 now supports managing SUSE Linux Micro 6.1 as client.

For more information about the registration process, refer to the Registration section, and for more information about supported features, consult the Supported Features.

Uyuni 2025.05 now supports managing SUSE Linux Enterprise 15 SP7 family as clients.

For details on the registration process, please refer to the Registration section. To learn more about supported features, consult the Supported Features section in our documentation.

Uyuni now allows users to configure Minion registration to use a MAC address instead of HW-TYPE-MACHINE-ID during the setup of Uyuni for Retail.

By using the MAC address in the registration string, each machine becomes uniquely identifiable, reducing confusion in scenarios such as network or boot issues, where multiple entries for the same hardware might have previously occurred.

This enhancement improves clarity and simplifies hardware identification and management within Uyuni for Retail environments.

Following updates have been made in the POS image templates

As an effort to support air-gapped environments, Uyuni now includes RPMs with the different images, for both Server and Proxy.

For further reference, please check the documentation in the section Air-gapped Deployment

Uyuni 2025.05 comes with a standalone Health Check tool. This tool provides a detailed dashboard, metrics, and logs from the server, showcasing its current health status based on the support-config. Users can efficiently evaluate the health of their running instance and identify any potential errors for effective troubleshooting.

The CVE Audit feature in Uyuni has traditionally relied on patch metadata from channels to identify affected systems.

With this release, Uyuni introduces a new and improved CVE Audit mechanism based on OVAL (Open Vulnerability and Assessment Language) data. This new approach allows for more precise and accurate vulnerability assessments by evaluating system packages directly against OVAL definitions.

This feature is currently released as a Technology Preview. Users can begin testing the OVAL-based CVE Audit to gain better insights into their systems' exposure to known vulnerabilities.

For more information, see Oval section.

In previous versions, Uyuni did not support password policy enforcement. Administrators could set any password for users, regardless of complexity.

With this release, administrators can now define and enforce password policies for Uyuni users. Once configured, the system ensures that all newly created user passwords adhere to the specified rules.

This helps organizations comply with internal security standards and improve overall password security.

The product migration feature has been enhanced, allowing users to seamlessly migrate their SUSE Linux Enterprise Server systems to SUSE Linux Enterprise Server for SAP when needed. This improvement significantly enhances the user experience, eliminating the need for specific scripts previously required, as it is now integrated into Uyuni’s capabilities.

Due to the changes introduced in this version, the Uyuni Documentation API has been upgraded from version 27 to 28.

This version removes the deprecated method synchronizeChannels from sync.content

For further details about the API, please refer to the Uyuni API Documentation.