Version Revision History
2023/03/02: 2023.03 release
2023/01/30: 2023.01 release
2022/12/20: 2022.12 release
2022/11/21: 2022.11 release
2022/10/14: 2022.10 release
2022/08/10: 2022.08 release
2022/06/26: 2022.06 release
2022/05/10: 2022.05 release
2022/04/29: 2022.04 release
2022/03/31: 2022.03 release
2022/02/28: 2022.02 release
2022/01/28: 2022.01 release
2021/12/09: 2021.12 release
You can stay up-to-date regarding information about Uyuni:
Check the home site https://www.uyuni-project.org
Uyuni is a community-supported project. The ways of contacting the community are available at the home site.
Uyuni uses a rolling release model (meaning there will be no bugfixing for given Uyuni version, but new frequent versions that will include bugfixes and features).
Check the home site get in contact with the community.
Major changes since Uyuni Proxy 2021.12
Features and changes
Salt 3000 EoL
Upstream Salt 3000 went End of life on August 31, 2021. However, because it was part of the Advanced Systems Management Module of SUSE Linux Enterprise 12 and there was no bundle available for SUSE Manager 4.1, it was still supported.
Salt 3000 will no longer be supported in the context of Uyuni now that both SUSE Manager 4.1 and the Advanced Systems Management Module of SUSE Linux Enterprise 12 are End of Life.
Users are required to migrate existing Salt 3000 minions for SUSE Linux Enterprise Server 12, Red Hat Enterprise Linux 7, CentOS 7, Oracle Linux 7, and Amazon Linux 2 to the Salt Bundle before creating any bug reports.
For more information about performing Salt 3000 to Salt Bundle migrations, please consult the Salt Bundle section in the Client Configuration Guide.
Release notes cleanup
With Uyuni 2023.01, we are removing versions older than 2021.12 from the release notes, to make the document smaller and easier to review.
Release notes for older versions, up to 4.0.0 can stil be found at the website.
Proxy deployment with Helm Charts
Technology Preview: Helm chart to deploy containerized Uyuni Proxy and Retail Branch Server
Deploying Proxy and Retail Branch Servers as containers is now also possible using a Helm chart.
For more information check this README file. The information will be part of the Uyuni official documentation in a future release.
WARNING: The container images configuration has a new format and it is now packaged as tar.gz file. All previously deployed container Proxies and Retail Branch Servers will need to get their configuration regenerated and deployed again before pulling these images.
WARNING: This release updates the base OS from openSUSE Leap 15.3 to openSUSE Leap 15.4 and there are special steps required. You need at least Uyuni 2021.06 already installed to perform the upgrade, and you need to follow the (major upgrade procedure for the Proxy. More details are also available at the "Update from previous versions of Uyuni Proxy" section below.
WARNING: This release updates the Salt version for master and minions to a next major release. Make sure you update the Uyuni Server before updating the proxies, as backward compatiblity of minions against an older master is not guaranteed
WARNING: With Uyuni 2021.12, we announced the future deprecation of the Traditional client tools. Uyuni 2022.06 is the last release that supports them. Starting with Uyuni 2022.08, the traditional client tools will be deprecated as we will start removing the code at some point after the summer. Do not use the traditional stack for any new deployments of clients or proxies, and start migrating your traditional clients to Salt.
Base system upgrade
The base system has been upgraded to openSUSE Leap 15.4.
Salt has been upgraded to upstream version 3004, plus a number of patches, backports and enhancements by SUSE, for the Uyuni Manager Server, Proxy, and Client Tools.
We intend to regularly upgrade Salt to more recent versions.
For more details about changes in your manually-created Salt states, see the Salt 3004 upstream release notes.
Salt Bundle 3004 will be available for all supported clients.
The non-bundle version of Salt requires Python3 instaled by default, so it will not be available for:
SUSE Linux Enteprise 12
Oracle Linux 7
Red Hat Enteprise Linux 7
HTTP Strict Transport Security (HSTS) is a policy mechanism that helps to protect websites against man-in-the-middle attacks such as protocol downgrade attacks and cookie hijacking.
Uyuni 2022.04 allows enabling HSTS. Which means each request will need to be HTTPS while plain HTTP requests will be rejected.
To enable it for the Uyuni Proxy:
Uncomment the line
# Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains"
Restart Apache with
systemctl restart apache2
IMPORTANT: If you enable HSTS while using the default SSL certificate generated by Uyuni, or a self-signed certificate, some browsers will refuse to connect using HTTPS unless the CA used to sign such certificates is trusted by the browser. If you are using the SSL certificate generated by Uyuni, you can trust it at the servers by using the file located at `http://<UYUNI-PROXY-HOSTNAME>/pub/RHN-ORG-TRUSTED-SSL-CERT
Technology Preview: Containerized SUSE Manager Proxy and Retail Branch Server
Starting with Uyuni 2022.04, it will be possible to run the Uyuni proxy and Retail branch server also in containers. This could be very helpful in scenarios where adding new virtual machines is not feasible for some reason.
Additionally, the ability to run Uyuni Proxy and Retail branch servers in containers make it more flexible to run them anywhere without worrying about the underlying OS, while also making it possible to get the advantage of Kubernetes offerings like HA.
Red Hat Enterprise Linux 6
SUSE Linux Enterprise Server Expanded Support 6
Oracle Linux 6
We highly encourage you to migrate your workload to a newer version of each distribution, or to an alternative distribution that is still supported, so you can continue managing your infrastructure with Uyuni.
Please note that we will not break things on purpose for these unsupported products, and there is a possibility that they could still continue to work. But if things break, there will not be any support provided, not even on a best-effort basis, unless someone from the community can step in.
Uyuni 2022.02 updates Prometheus from version 2.27.1 to 2.32.1.
The new version contains some breaking changes that need to be addressed after the Uyuni Server is updated.
Uyuni Service Discovery: The configuration and the returned set of meta labels have changed. Please check the upstream documentation for more details.
As a consequence all users with existing monitoring setup must reapply the highstate on the monitoring server(s).
Introduced generic HTTP-based service discovery.
New expression editor with advanced autocompletion, inline linting, and syntax highlighting.
Discovering Kubernetes API servers using a kubeconfig file.
Faster server restart times via snapshotting.
Controlling scrape intervals and timeouts via relabeling.
Check the upstream changelog for more details on what has changed.
Change proxy used for clients from the WebUI
It is now possible to change the proxy used by an Uyuni client using the WebUI.
This can be done from the
Connection tab at the
Details tab for any Salt client, using the new link
Change to change the connection type.
Using System Set Manager is supported as well, and can be done from the
Misc tab, and then
NOTE: Changing the connection for a Proxy to move it, is not supported at this moment. The Connectiontab will not show the
Change link for proxies.
Salt as a Bundle
Salt Bundle is a single package called
venv-salt-minion containing the Salt Minion, Python and all Python modules. It is exactly the same version and codebase for the current
salt-minion RPM package.
The Salt Bundle can be used on systems that already run another Salt Minion, that do not meet Salt’s requirements or already provide a newer salt version that is used instead of the version provided by Uyuni.
Starting with Uyuni 2021.12, Uyuni is able to bootstrap systems with Salt Bundle for all the supported operating systems.
On bootstrapping new proxies the Salt Bundle package will be used instead of salt-minion, if the package
venv-salt-minion is present in the bootstrap repo.
Proxies already registered will not be changed, but can be switched to Salt Bundle with applying the state
util.mgr_switch_to_venv_minion to them.
Prometheus Blackbox exporter
Uyuni 2021.12 comes with the Blackbox exporter, which allows blackbox probing of endpoints over HTTP, HTTPS, DNS, TCP, and ICMP. It needs to be installed next to the Prometheus server and not on the clients. Prometheus formula has been extended to configure the Blackbox exporter.
The package prometheus-blackbox_exporter has been added as recommended for the Proxy.
One of the limitations of the current formulas is that they are listed against every client, even if the supported packages are not available for that OS version or service pack.
While we are continuously focused on improving the formulas, for now, starting with the monitoring formulas it will be mentioned in documentation if applying those formulas would actually work in the case of a particular client.
In 2021.09, we made the Prometheus package available for Uyuni Proxy and Retail Branch Server but that is not the case with Grafana.
Prometheus is available for the client tools for SLE 12, SLE 15, and openSUSE 15 Uyuni Proxies or Retail Branch Servers
Grafana is available for the client tools for SLE 12, SLE 15, openSUSE15
New product enabled
SUSE Linux Enterprise Server 15 SP2 LTSS
CentOS 8 End of Life
CentOS 8 will be End of Life on December 31st, 2021. Uyuni support for this product will end as well.
Please refer to support section for more information.
Future deprecation of the traditional stack
With Uyuni 2021.12, we announced the future deprecation of the Traditional client tools.
Uyuni 2022.06 is the last release that supportes them.
Starting with Uyuni 2022.08, the traditional client tools will be deprecated as we will start removing the code to support them at some point after the summer.
Do not use traditional for any new deployments of clients or proxies, and start migrating your traditional clients to Salt.
Installing the Proxy
Installation of Uyuni Proxy is done via the Uyuni Server web interface.
See the Installation/Upgrade guide for step-by-step instructions on how to install and configure the Uyuni Proxy.
The repository for the Proxy is https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/images/repo/Uyuni-Proxy-POOL-x86_64-Media1/
Update from previous versions of Uyuni Proxy
When updating, always start with the server first and then continue with the proxies.
See the Installation/Upgrade guide for detailed instructions on how to upgrade.
If you are upgrading from 2022.05 or earlier (at least 2021.06): You will need to follow the "Installation/Upgrade Guide > Upgrade > Upgrade the Proxy" > "Proxy - Major Upgrade" section.
If you are updating from 2022.06 or newer: You will need to follow the "Installation/Upgrade Guide > Upgrade > Upgrade the Proxy" > "Proxy - Minor Upgrade" section.
Migrating from versions older than 2022.06 is possible only with a proxy replacement, as described at the documentation.
Single Sign On, API and CLI tools
Single Sign On can be used to authenticate in the Web UI but not with the API or CLI tools. This will be fixed in a future release of Uyuni.
In case of encountering a bug please report it at https://github.com/uyuni-project/uyuni/issues
Copyright © 2018 – 2023 The Uyuni Project and contributors. All rights reserved.
This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/es/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.
For SUSE trademarks, see http://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this document has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.