Version Revision History
2018/10/26: 4.0.0 release
2018/12/19: 4.0.1 release
You can stay up-to-date regarding information about Uyuni:
Check the home site https://www.uyuni-project.org
Uyuni is a community support project. The ways or 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 4.0.0
Features and changes
Support for PostgreSQL 10
A new version of the PostgreSQL database is available in openSUSE Leap 42.3 and can be used for Uyuni Server.
New installations of Uyuni Server based on openSUSE Leap 42.3 will automatically pick up this version.
PostgreSQL 10 needs a new version of smdba to initiate backups. This version is part of Uyuni Server 4.0.1.
Migrating from PostgreSQL 9.6 to PostgreSQL 10
You should have an up-to-date database backup before attempting the migration.
Existing installations of Uyuni Server will need to run
to migrate from PostgreSQL 9.6 to PostgreSQL 10
Your Uyuni Server installation will not be accessible during the migration.
Note The migration will create a copy of the database under
/var/lib/pgsql and thus needs sufficient disk space to hold two copies
(9.6 and 10) of the database.
Since it does a full copy of the database, it also needs considerable time depending on the size of the database and the IO speed of the storage.
If your system is scarce on disk space you can do an fast, in-place migration by running
The fast migration usually only takes minutes and no additional disk space. However, in case of failure you need to restore the database from a backup.
This wiki page contains additional information about the database migration.
spacecmd: Support state channels
spacecmd, the command line access to the Uyuni API, has been adapted
to support state channels (aka Salt Minion config channels) with the
new call to schedule application of the assigned config channels to the system (minion only)
new call to update the
adapted call, now has a
-toption to specify the channel type (
adapted call, honors channel type
Please use the help functionality of spacecmd for detailed option descriptions for each mentioned call.
New API calls
to merge packages and errata through spacecmd were added.
spacewalk-common-channels: Support for Uyuni, Fedora 29 and cleanup
Added: - Uyuni Server, Uyuni Proxy, Uyuni Client Tools, both stable and development version. - Fedora 29
Removed: - Fedora 26 - Spacewalk 2.6 Server and Client Tools - Spacewalk 2.7 Server and Client Tools - Spacewalk 2.8 Server - Spacewalk nightly - OpenSUSE 13.2 and openSUSE 13.2 Client Tools
Support for more Distributions as Clients
openSUSE Leap 15.0, openSUSE Leap 42.3, SLE12, SLE15, CentOS6 and CentOS7 are now verified to bootstrap as both salt minions and traditional clients.
New products added to SCC syncing
SUSE OpenStack Cloud 9
Client Tools Notes
All Client Tools are still considered "Beta" and there could still be dependencies problems, notably for SLE12 and CentOS6 and CentOS7.
URLs of the Client Tools are:
SLE12 (x86_64, pcc64le. s390x, aarch64): https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable:/SLE12-Uyuni-Client-Tools/SLE_12/
SLE15 (x86_64, pcc64le. s390x, aarch64): https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable:/SLE15-Uyuni-Client-Tools/SLE_15
At the moment the status is the following:
Salt bootstrap from server
Salt SSH bootstrap from server
Salt bootstrap from client
openSUSE Leap 42.3
openSUSE Leap 15.0
= Working, = Not working, = Untested
RHEL6 and RHEL7 are expected to work in the same way CentOS6 and CentOS7. Client Tools repositories for a CentOS version should work at the respective RHEL version.
The GPG key for Uyuni Client Tools is not trusted by default by neither openSUSE, SLE or CentOS.
The systems will bootstrap without the GPG key being trusted, but will not be able to install new client tool packages or updated them.
This can be fixed by adding the key
uyuni-gpg-pubkey-0d20833e.key to all the bootscrap scripts at
ORG_GPG_KEY=. If you already have other keys there, you can keep them.
For systems bootstrapped from WebUI, a salt state should be created to trust the key, then the state can be assigned to the organization, and finally it can be used using an Activation Key and the Configuration Channels to deploy the change to the clients.
It is usable but you can still find some issues, such references to SUSE Manager that are scheduled to be fixed on subsequent versions.
OS: openSUSE Leap 42.3 x86_64, fully updated
Main memory: Minimum 16 GB for base installation
Disk space: Minimum 100 GB for root partition, Minimum 50 GB for /var/lib/pgsql, Minimum 50 GB per SUSE product + 100 GB per RHEL product (/var/spacewalk)
See the Getting Started manual for more details on the system requirements.
Installing the Server
Add the Stable repository:
Install the pattern:
zypper in patterns-uyuni_server
Run Yast2 and go to Network Services > Uyuni Setup
Follow the setup assistant.
Update from previous versions of Uyuni Server
You can update from previous Uyuni Server Stable versions.
See the best practices manual for detailed instructions on how to upgrade.
All connected clients will continue to run and are manageable unchanged.
Uyuni Proxy versions
Uyuni Proxy 4.0.1 can work with Uyuni Server 4.0.1
When upgrading, start with the server first and then continue with the proxies. See the advanced topics manual for detailed upgrade instructions.
Red Hat Channels
Managing RHEL clients requires availability of appropriate Red Hat packages.
Managing SUSE Linux clients requires availability of appropriate SUSE channels.
Your licensed SUSE products can be used with Uyuni by following the setup Wizard.
Check the manuals for more information.
In case of encountering a bug please report it at https://github.com/uyuni-project/uyuni/issues
Copyright © 2012 – 2018 SUSE LLC 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.