Did you fully upgrade the server? What's the changelog of the reprepro package? IIRC we had to fix this package so it could handle the new zstd compresed control file, and the fix is part of 2022.08: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... $ rpm -q --changelog reprepro-5.3.0-2.8.uyuni2.x86_64.rpm|more * mié jun 29 2022 Julio González Gil - Bump up the maxsize on a fixed-size C buffer to avoid breaking on some autogenerated rust packages * 0001-Bump-up-the-maxsize-on-a-fixed-size-C-buffer-to-avoi.patch - Flush stdout and stderr before execv of an end hook * 0002-Flush-stdout-stderr-before-calling-endhook.patch - Add support for Zstd compressed debs * 0003-Add-Zstd-support.patch If you don't have this changelog entry, and if you already updated your server, maybe be the mirror you used still didn't have the reprepro version? El jueves, 11 de agosto de 2022 11:28:54 (CEST) Paul-Andre Panon via Uyuni Users escribió:

That's excellent! I was worried we might have to wait longer for Ubuntu 22.04 support after the lack of a 2022.07 release. Thank you.

That said, when I tried to create an Ubuntu 22.04 bootstrap repo, I got the following error message:

# mgr-create-bootstrap-repo --create ubuntu-22.04-amd64-uyuni

Creating bootstrap repo for ubuntu-22.04-amd64-uyuni copy 'venv-salt-minion-3004-4.6.uyuni.amd64-deb' Could not find a suitable control.tar file within '/srv/www/htdocs/pub/repositories/ubuntu/22/4/bootstrap.tmp/debs/venv-salt- minion-3004-4.6.uyuni.amd64-deb.deb'! There have been errors! Error creating bootstrap repo.

Could it be that that function isn't benefiting from the updates to support the new compression algorithm used for Ubuntu 22.04 packages?

Cheers,

Paul-Andre

-----Original Message----- From: Julio Gonzalez via Uyuni Users Sent: Wednesday, August 10, 2022 4:07 AM To: announce@lists.uyuni-project.org; devel@lists.uyuni-project.org; users@lists.uyuni-project.org Cc: Julio Gonzalez Subject: Uyuni 2022.08 is released!

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also needs to be updated. Make sure you read the release notes before updating!

We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced.

At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions.

This is the list of highlights for this release:

- Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy and Retail Branch Server

Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2022.08

As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute.

Happy hacking!

[1] https://www.uyuni-project.org/pages/contact.html

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

Just chipping in. I don't have the original mgr-create-bootstrap-repo error, but during the upgrade from 2022.06 to 08, I also have some files that weren't upgraded. === The following 3 package updates will NOT be installed: cobbler netty supportutils-plugin-salt Nothing to do. === Attempting to update them manually gives me options, but I'm unsure what to do. Uyuni itself seems to be operating normally since the upgrade. === ata-oxy-uyuni01:/home/simon # zypper install cobbler netty supportutils-plugin-salt Loading repository data... Reading installed packages... 'netty' is already installed. There is an update candidate for 'netty' from vendor 'SUSE LLC https://www.suse.com/', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install netty-4.1.75-150200.4.9.1.x86_64' to install this candidate. 'cobbler' is already installed. There is an update candidate for 'cobbler' from vendor 'openSUSE', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install cobbler-3.3.1.0+git.f5b0599a-bp154.1.26.noarch' to install this candidate. 'supportutils-plugin-salt' is already installed. There is an update candidate for 'supportutils-plugin-salt' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install supportutils-plugin-salt-1.2.1-1.4.uyuni2.noarch' to install this candidate. Resolving package dependencies... Nothing to do. === -----Original Message----- From: Paul-Andre Panon via Uyuni Users Sent: 12 August 2022 17:58 To: Julio Gonzalez ; General discussion related to the openSUSE Uyuni project Cc: Paul-Andre Panon Subject: [EXTERNAL EMAIL] RE: Uyuni 2022.08 is released! Well, two packages aren't updated because there appears to be duplicate packages from different repos for netty and cobbler. # zypper update Loading repository data... Reading installed packages... The following 2 package updates will NOT be installed: cobbler netty Nothing to do. # zypper install cobbler netty Loading repository data... Reading installed packages... 'netty' is already installed. There is an update candidate for 'netty' from vendor 'SUSE LLC https://www.suse.com/', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install netty-4.1.75-150200.4.9.1.x86_64' to install this candidate. 'cobbler' is already installed. There is an update candidate for 'cobbler' from vendor 'openSUSE', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install cobbler-3.3.1.0+git.f5b0599a-bp154.1.26.noarch' to install this candidate. Resolving package dependencies... Nothing to do. I've been assuming that Uyuni vendor packages are the correct ones. If I try use the zipper install command above then it indicates a whole bunch of Uyuni package dependencies would get removed, so I'm fairly sure the one currently installed is the right one. # zypper install netty-4.1.75-150200.4.9.1.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the installed spacewalk-java-4.3.35-1.12.uyuni2.noarch requires 'netty < 4.1.45', but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of spacewalk-java-4.3.35-1.12.uyuni2.noarch deinstallation of spacewalk-common-4.3.5-1.12.uyuni2.noarch deinstallation of spacewalk-postgresql-4.3.5-1.12.uyuni2.noarch deinstallation of susemanager-tools-4.3.18-1.11.uyuni2.x86_64 deinstallation of patterns-uyuni_server-2022.08-2.2.uyuni2.x86_64 deinstallation of susemanager-4.3.18-1.11.uyuni2.x86_64 deinstallation of spacewalk-backend-tools-4.3.15-1.10.uyuni2.noarch deinstallation of supportutils-plugin-susemanager-4.3.4-1.24.uyuni2.noarch deinstallation of spacewalk-setup-4.3.10-1.2.uyuni2.noarch deinstallation of spacewalk-utils-4.3.13-1.6.uyuni2.noarch Solution 2: do not install netty-4.1.75-150200.4.9.1.x86_64 Solution 3: break spacewalk-java-4.3.35-1.12.uyuni2.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Otherwise, the server appears up-to-date, has been rebooted, and we get the error. That said the reprepro does seem different than the version you indicated. # rpm -q -i reprepro Name : reprepro Version : 5.3.0 Release : 2.33.uyuni2 Architecture: x86_64 Install Date: Tue Jun 28 15:25:55 2022 Group : System/Packages Size : 1179511 License : GPL-2.0 Signature : RSA/SHA256, Wed Jun 22 09:25:40 2022, Key ID 972e5d6c0d20833e Source RPM : reprepro-5.3.0-2.33.uyuni2.src.rpm Build Date : Wed Jun 22 09:25:33 2022 Build Host : lamb02 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : obs://build.opensuse.org/systemsmanagement:Uyuni URL : https://salsa.debian.org/brlink/reprepro Summary : Handle local repositories of debian packages Description : This project is a lightweight feature complete manager of a debian package (i.e. binary .deb and source .dsc+.tar.gz+.diff.gz) repository. Emphasis is put on having all packages in the pool/-directory, maximal checking of all sources, generation of signed Release file, Contents, ... Distribution: systemsmanagement:Uyuni:Master / openSUSE_Leap_15.4 -----Original Message----- From: Julio Gonzalez Sent: Thursday, August 11, 2022 2:35 AM To: General discussion related to the openSUSE Uyuni project Cc: Paul-Andre Panon ; Paul-Andre Panon via Uyuni Users Subject: Re: Uyuni 2022.08 is released! Did you fully upgrade the server? What's the changelog of the reprepro package? IIRC we had to fix this package so it could handle the new zstd compresed control file, and the fix is part of 2022.08: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... $ rpm -q --changelog reprepro-5.3.0-2.8.uyuni2.x86_64.rpm|more * mié jun 29 2022 Julio González Gil - Bump up the maxsize on a fixed-size C buffer to avoid breaking on some autogenerated rust packages * 0001-Bump-up-the-maxsize-on-a-fixed-size-C-buffer-to-avoi.patch - Flush stdout and stderr before execv of an end hook * 0002-Flush-stdout-stderr-before-calling-endhook.patch - Add support for Zstd compressed debs * 0003-Add-Zstd-support.patch If you don't have this changelog entry, and if you already updated your server, maybe be the mirror you used still didn't have the reprepro version? El jueves, 11 de agosto de 2022 11:28:54 (CEST) Paul-Andre Panon via Uyuni Users escribió:

That's excellent! I was worried we might have to wait longer for Ubuntu 22.04 support after the lack of a 2022.07 release. Thank you.

That said, when I tried to create an Ubuntu 22.04 bootstrap repo, I got the following error message:

# mgr-create-bootstrap-repo --create ubuntu-22.04-amd64-uyuni

Creating bootstrap repo for ubuntu-22.04-amd64-uyuni copy 'venv-salt-minion-3004-4.6.uyuni.amd64-deb' Could not find a suitable control.tar file within '/srv/www/htdocs/pub/repositories/ubuntu/22/4/bootstrap.tmp/debs/venv- salt- minion-3004-4.6.uyuni.amd64-deb.deb'! There have been errors! Error creating bootstrap repo.

Could it be that that function isn't benefiting from the updates to support the new compression algorithm used for Ubuntu 22.04 packages?

Cheers,

Paul-Andre

-----Original Message----- From: Julio Gonzalez via Uyuni Users Sent: Wednesday, August 10, 2022 4:07 AM To: announce@lists.uyuni-project.org; devel@lists.uyuni-project.org; users@lists.uyuni-project.org Cc: Julio Gonzalez Subject: Uyuni 2022.08 is released!

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also needs to be updated. Make sure you read the release notes before updating!

We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced.

At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions.

This is the list of highlights for this release:

- Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy and Retail Branch Server

Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2022.08

As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute.

Happy hacking!

[1] https://www.uyuni-project.org/pages/contact.html

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

Thanks for the prompt clarification, Julio. Leaving them be. -----Original Message----- From: Julio Gonzalez Sent: 16 August 2022 09:41 To: General discussion related to the openSUSE Uyuni project ; Simon Avery Cc: Paul-Andre Panon Subject: [EXTERNAL EMAIL] Re: Uyuni 2022.08 is released! Hi all, Never change the vendor for packages, unless we ask for it at the release notes. Doing it can render Uyuni unusable. There are some packages we require strictly from our repositories. Best regards. El martes, 16 de agosto de 2022 10:32:15 (CEST) Simon Avery escribió:

Just chipping in.

I don't have the original mgr-create-bootstrap-repo error, but during the upgrade from 2022.06 to 08, I also have some files that weren't upgraded.

=== The following 3 package updates will NOT be installed: cobbler netty supportutils-plugin-salt Nothing to do. ===

Attempting to update them manually gives me options, but I'm unsure what to do. Uyuni itself seems to be operating normally since the upgrade.

=== ata-oxy-uyuni01:/home/simon # zypper install cobbler netty supportutils-plugin-salt Loading repository data... Reading installed packages... 'netty' is already installed. There is an update candidate for 'netty' from vendor 'SUSE LLC https://www.suse.com/', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install netty-4.1.75-150200.4.9.1.x86_64' to install this candidate. 'cobbler' is already installed. There is an update candidate for 'cobbler' from vendor 'openSUSE', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install cobbler-3.3.1.0+git.f5b0599a-bp154.1.26.noarch' to install this candidate. 'supportutils-plugin-salt' is already installed. There is an update candidate for 'supportutils-plugin-salt' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install supportutils-plugin-salt-1.2.1-1.4.uyuni2.noarch' to install this candidate. Resolving package dependencies... Nothing to do. ===

-----Original Message----- From: Paul-Andre Panon via Uyuni Users Sent: 12 August 2022 17:58 To: Julio Gonzalez ; General discussion related to the openSUSE Uyuni project Cc: Paul-Andre Panon Subject: [EXTERNAL EMAIL] RE: Uyuni 2022.08 is released!

Well, two packages aren't updated because there appears to be duplicate packages from different repos for netty and cobbler.

# zypper update Loading repository data... Reading installed packages...

The following 2 package updates will NOT be installed: cobbler netty Nothing to do.

# zypper install cobbler netty Loading repository data... Reading installed packages... 'netty' is already installed. There is an update candidate for 'netty' from vendor 'SUSE LLC https://www.suse.com/', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install netty-4.1.75-150200.4.9.1.x86_64' to install this candidate. 'cobbler' is already installed. There is an update candidate for 'cobbler' from vendor 'openSUSE', while the current vendor is 'obs://build.opensuse.org/systemsmanagement:Uyuni'. Use 'zypper install cobbler-3.3.1.0+git.f5b0599a-bp154.1.26.noarch' to install this candidate. Resolving package dependencies... Nothing to do.

I've been assuming that Uyuni vendor packages are the correct ones. If I try use the zipper install command above then it indicates a whole bunch of Uyuni package dependencies would get removed, so I'm fairly sure the one currently installed is the right one.

# zypper install netty-4.1.75-150200.4.9.1.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies...

Problem: the installed spacewalk-java-4.3.35-1.12.uyuni2.noarch requires 'netty < 4.1.45', but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of spacewalk-java-4.3.35-1.12.uyuni2.noarch deinstallation of spacewalk-common-4.3.5-1.12.uyuni2.noarch deinstallation of spacewalk-postgresql-4.3.5-1.12.uyuni2.noarch deinstallation of susemanager-tools-4.3.18-1.11.uyuni2.x86_64 deinstallation of patterns-uyuni_server-2022.08-2.2.uyuni2.x86_64 deinstallation of susemanager-4.3.18-1.11.uyuni2.x86_64 deinstallation of spacewalk-backend-tools-4.3.15-1.10.uyuni2.noarch deinstallation of supportutils-plugin-susemanager-4.3.4-1.24.uyuni2.noarch deinstallation of spacewalk-setup-4.3.10-1.2.uyuni2.noarch deinstallation of spacewalk-utils-4.3.13-1.6.uyuni2.noarch Solution 2: do not install netty-4.1.75-150200.4.9.1.x86_64 Solution 3: break spacewalk-java-4.3.35-1.12.uyuni2.noarch by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c

Otherwise, the server appears up-to-date, has been rebooted, and we get the error. That said the reprepro does seem different than the version you indicated.

# rpm -q -i reprepro Name : reprepro Version : 5.3.0 Release : 2.33.uyuni2 Architecture: x86_64 Install Date: Tue Jun 28 15:25:55 2022 Group : System/Packages Size : 1179511 License : GPL-2.0 Signature : RSA/SHA256, Wed Jun 22 09:25:40 2022, Key ID 972e5d6c0d20833e Source RPM : reprepro-5.3.0-2.33.uyuni2.src.rpm Build Date : Wed Jun 22 09:25:33 2022 Build Host : lamb02 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : obs://build.opensuse.org/systemsmanagement:Uyuni URL : https://salsa.debian.org/brlink/reprepro Summary : Handle local repositories of debian packages Description : This project is a lightweight feature complete manager of a debian package (i.e. binary .deb and source .dsc+.tar.gz+.diff.gz) repository. Emphasis is put on having all packages in the pool/-directory, maximal checking of all sources, generation of signed Release file, Contents, ... Distribution: systemsmanagement:Uyuni:Master / openSUSE_Leap_15.4

-----Original Message----- From: Julio Gonzalez Sent: Thursday, August 11, 2022 2:35 AM To: General discussion related to the openSUSE Uyuni project Cc: Paul-Andre Panon ; Paul-Andre Panon via Uyuni Users Subject: Re: Uyuni 2022.08 is released!

Did you fully upgrade the server?

What's the changelog of the reprepro package?

IIRC we had to fix this package so it could handle the new zstd compresed control file, and the fix is part of 2022.08:

https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/S table/ images/repo/Uyuni-Server-POOL-x86_64-Media1/x86_64/reprepro-5.3.0-2.8. uyuni2 .x86_64.rpm

$ rpm -q --changelog reprepro-5.3.0-2.8.uyuni2.x86_64.rpm|more * mié jun 29 2022 Julio González Gil - Bump up the maxsize on a fixed-size C buffer to avoid breaking on some autogenerated rust packages * 0001-Bump-up-the-maxsize-on-a-fixed-size-C-buffer-to-avoi.patch - Flush stdout and stderr before execv of an end hook * 0002-Flush-stdout-stderr-before-calling-endhook.patch - Add support for Zstd compressed debs * 0003-Add-Zstd-support.patch

If you don't have this changelog entry, and if you already updated your server, maybe be the mirror you used still didn't have the reprepro version? El jueves, 11 de agosto de 2022 11:28:54 (CEST) Paul-Andre Panon via Uyuni Users escribió:

...

That's excellent! I was worried we might have to wait longer for Ubuntu 22.04 support after the lack of a 2022.07 release. Thank you.

That said, when I tried to create an Ubuntu 22.04 bootstrap repo, I got the following error message:

# mgr-create-bootstrap-repo --create ubuntu-22.04-amd64-uyuni

Creating bootstrap repo for ubuntu-22.04-amd64-uyuni copy 'venv-salt-minion-3004-4.6.uyuni.amd64-deb' Could not find a suitable control.tar file within '/srv/www/htdocs/pub/repositories/ubuntu/22/4/bootstrap.tmp/debs/ven v- salt- minion-3004-4.6.uyuni.amd64-deb.deb'! There have been errors! Error creating bootstrap repo.

Could it be that that function isn't benefiting from the updates to support the new compression algorithm used for Ubuntu 22.04 packages?

Cheers,

Paul-Andre

-----Original Message----- From: Julio Gonzalez via Uyuni Users Sent: Wednesday, August 10, 2022 4:07 AM To: announce@lists.uyuni-project.org; devel@lists.uyuni-project.org; users@lists.uyuni-project.org Cc: Julio Gonzalez Subject: Uyuni 2022.08 is released!

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also needs to be updated. Make sure you read the release notes before updating!

We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few hours until your local openSUSE mirror is synced.

At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions.

This is the list of highlights for this release:

- Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy

and Retail Branch Server

Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2022.08

As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute.

Happy hacking!

[1] https://www.uyuni-project.org/pages/contact.html

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com

Hello all I have created a new certificate for my internal Uyuni server using Let's encrypt. But I have some trouble to activate this certificate: # mgr-ssl-cert-setup --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem Root CA is required I'm not the issue - there ars some certificates on https://letsencrypt.org/certificates/ With R3: # mgr-ssl-cert-setup --root-ca-file=/home/certs/lets-encrypt-r3.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Let's Encrypt, CN = R3' With fullchain.pem from Let's encrypt: # mgr-ssl-cert-setup --root-ca-file=/home/certs/fullchain.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Internet Security Research Group, CN = ISRG Root X1'' Some ideas? The certificate is valid - I can use it as apache certificate for the uyuni website and the browser says it is ok :) Best regards Martin

Hi I tried it with the intermediate (cross-signed and self-signed): $> mgr-ssl-cert-setup --root-ca-file=/home/certs/isrg-root-x1-cross-signed.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Internet Security Research Group, CN = ISRG Root X1' $> mgr-ssl-cert-setup --root-ca-file=/home/certs/isrgrootx1.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem ERROR: 'authorityKeyIdentifier' I can create a test certificate for you. The certificate I use is a wildcard certificate - could that make a difference? Best regards Martin Am 16.08.22 um 16:27 schrieb Michael Calmer:

Hi

Looking at the picture at https://letsencrypt.org/certificates/

you need 2 CAs. R3 which is an intermediate CA and ISGR Root X1 which seems to be the Root CA.

$> mgr-ssl-cert-setup --root-ca-file=/home/certs/lets-encrypt-isgr-x1.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem

It might be that there is a bug, but I would need such certificates to test it. (The private key should not be send. I can test without the key)

Regards

Michael

Am Dienstag, 16. August 2022, 14:14:21 CEST schrieb Martin:

...

Hello all

I have created a new certificate for my internal Uyuni server using Let's encrypt.

But I have some trouble to activate this certificate:

# mgr-ssl-cert-setup --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem Root CA is required

I'm not the issue - there ars some certificates on https://letsencrypt.org/certificates/

With R3:

# mgr-ssl-cert-setup --root-ca-file=/home/certs/lets-encrypt-r3.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem

ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Let's Encrypt, CN = R3'

With fullchain.pem from Let's encrypt:

# mgr-ssl-cert-setup --root-ca-file=/home/certs/fullchain.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem

ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Internet Security Research Group, CN = ISRG Root X1''

Some ideas?

The certificate is valid - I can use it as apache certificate for the uyuni website and the browser says it is ok :)

Best regards

Martin

Hello Michael After using the fix from the GIT it worked for me too Thank you! Best regards Martin Am 23.08.22 um 16:56 schrieb Michael Calmer:

Hi

Seems somebody else reported this issue in github

https://github.com/uyuni-project/uyuni/issues/5830

Follow that to find fixes soon.

Am Dienstag, 16. August 2022, 18:06:12 CEST schrieb Martin:

...

Hi

I tried it with the intermediate (cross-signed and self-signed):

$> mgr-ssl-cert-setup --root-ca-file=/home/certs/isrg-root-x1-cross-signed.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem

ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Internet Security Research Group, CN = ISRG Root X1'

$> mgr-ssl-cert-setup --root-ca-file=/home/certs/isrgrootx1.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem

ERROR: 'authorityKeyIdentifier'

I can create a test certificate for you. The certificate I use is a wildcard certificate - could that make a difference?

Best regards

Martin

Am 16.08.22 um 16:27 schrieb Michael Calmer:

...

Hi

Looking at the picture at https://letsencrypt.org/certificates/

you need 2 CAs. R3 which is an intermediate CA and ISGR Root X1 which seems to be the Root CA.

$> mgr-ssl-cert-setup --root-ca-file=/home/certs/lets-encrypt-isgr-x1.pem \ --intermediate-ca-file=/home/certs/lets-encrypt-r3.pem \ --server-cert-file=/home/certs/uyuni.crt.pem \ --server-key-file=/home/certs/uyuni.key.pem

It might be that there is a bug, but I would need such certificates to test it. (The private key should not be send. I can test without the key)

Regards

Michael

Am Dienstag, 16. August 2022, 14:14:21 CEST schrieb Martin:

...

Hello all

I have created a new certificate for my internal Uyuni server using Let's encrypt.

But I have some trouble to activate this certificate:

# mgr-ssl-cert-setup --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem Root CA is required

I'm not the issue - there ars some certificates on https://letsencrypt.org/certificates/

With R3:

# mgr-ssl-cert-setup --root-ca-file=/home/certs/lets-encrypt-r3.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem

ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Let's Encrypt, CN = R3'

With fullchain.pem from Let's encrypt:

# mgr-ssl-cert-setup --root-ca-file=/home/certs/fullchain.pem --server-cert-file=/home/certs/uyuni.crt.pem --server-key-file=/home/certs/uyuni.key.pem

ERROR: Incomplete CA Chain. Unable to find issuer of 'C = US, O = Internet Security Research Group, CN = ISRG Root X1''

Some ideas?

The certificate is valid - I can use it as apache certificate for the uyuni website and the browser says it is ok :)

Best regards

Martin

El jueves, 11 de agosto de 2022 13:20:28 (CEST) Martin via Uyuni Users 
escribió:
> Hallo all
> 
> I can't connect to uyuni-stable repo:
> 
> uyuni:~ # zypper ref -s
> All services have been refreshed.
> Repository 'Update repository of openSUSE Backports' is up to date.
> Repository 'Non-OSS Repository' is up to date.
> Repository 'Haupt-Repository' is up to date.
> Repository 'Update repository with updates from SUSE Linux Enterprise 
> 15' is up to date.
> Repository 'Hauptaktualisierungs-Repository' is up to date.
> Repository 'Aktualisierungs-Repository (Nicht-Open-Source-Software)' is 
> up to date.
> Retrieving repository 'uyuni-server-stable' metadata 
> ............................................................................
> ......................[error]
 Repository 'uyuni-server-stable' is invalid.
> [uyuni-server-stable|https://download.opensuse.org/repositories/systemsmanag
> ement:/Uyuni:/Stable/images/repo/Uyuni-Server-POOL-x86_64-Media1/] 
 Valid
> metadata not found at specified URL
> History:
>   - [|] Error trying to read from 
> 'https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable
> /images/repo/Uyuni-Server-POOL-x86_64-Media1/'
 - Download (curl) error for
> 'https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable
> /images/repo/Uyuni-Server-POOL-x86_64-Media1/content':
 Error code: Curl
> error 60
>     Error message: SSL certificate problem: unable to get local issuer 
> certificate
> 
> Please check if the URIs defined for this repository are pointing to a 
> valid repository.
> Skipping repository 'uyuni-server-stable' because of the above error.
> Some of the repositories have not been refreshed because of an error.

curl -v https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/
Stable/images/repo/Uyuni-Server-POOL-x86_64-Media1/repodata/repomd.xml

and inspect the output

The repomd.xml doesn't get you redirected to a mirror, and works fine from 
here. But curl will give you more info about what's wrong.

In my case I see:

 Server certificate:
*  subject: CN=opensuse.org
*  start date: Jul 12 00:12:58 2022 GMT
*  expire date: Oct 10 00:12:57 2022 GMT
*  subjectAltName: host "download.opensuse.org" matched cert's 
"*.opensuse.org"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.

> Two additional Questions
> 
> What I have to do, if the uyuni server IP has changed?

AFAIK, as long as you keep the same hostname, you don't need to do anything.

If you also changed the hostname:
https://www.uyuni-project.org/uyuni-docs/en/uyuni/administration/
troubleshooting/tshoot-hostname-rename.html

> What I have to do, if the IP of a uyuni managed client has changed?

AFAI; if you onboarded using the clients hostname (recommended), nothing 
particular. At some point a refresh will happen and you will see the new IPs 
at the UI.

But if you onboarded using the IP of the clients, then I think (but I am not 
sure), that you need to use reactivation keys.

https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/
activation-keys.html#_reactivation_keys

> We move our servers to a new IP Range.

As long as you are using hostnames in all cases, chaging IPs should not really 
big an issue

 
> Best regards
> 
> Martin
> 
> Am 10.08.22 um 13:07 schrieb Julio Gonzalez via Uyuni Users:
> 
> > VERY IMPORTANT: 2022.08 requires special procedures if you are not
> > already
> > using Uyuni 2022.06! The configuration files for the proxy on containers
> > also
 needs to be updated. Make sure you read the release notes before
> > updating!>
> >
> >
> > We are happy to announce the availability of Uyuni 2022.08. Most openSUSE
> > mirrors should already have 2022.08, but if you do not see it yet, wait a
> > few
 hours until your local openSUSE mirror is synced.
> >
> >
> >
> > Athttps://www.uyuni-project.org/pages/stable-version.html  you will find
> > all
 the resources you need to start working with Uyuni 2022.08,
> > including the release notes, documentation, requirements and setup
> > instructions.>
> >
> >
> > This is the list of highlights for this release:
> >
> >
> >
> > - Ubuntu 22.04 as client
> > - GPG key handling in Uyuni
> > - Disabling locally defined repositories
> > - Technology Preview: Helm chart to deploy containerized Uyuni Proxy
> > 
> >    and Retail Branch Server
> >
> >
> >
> > Remember that Uyuni will follow a rolling release planning, so the next
> > version will contain bugfixes for this one and any new features. There
> > will be
 no maintenance of 2022.08
> >
> >
> >
> > As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of
> > you
 to send us your feedback [1] and of course your patches, if you can
> > contribute.
> >
> >
> >
> > Happy hacking!
> >
> >
> >
> > [1]https://www.uyuni-project.org/pages/contact.html


-- 
Julio González Gil
Release Engineer, SUSE Manager and Uyuni
jgonzalez@suse.com

Martin, could you please to check the output of the following command also: echo | openssl s_client -connect download.opensuse.org:443 Victor On Thu, 2022-08-11 at 17:50 +0200, Martin via Uyuni Users wrote:

Hello Julio

uyuni:~ # curl -v https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... *   Trying 195.135.221.134:443... * Connected to download.opensuse.org (195.135.221.134) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: unable to get local issuer certificate * Closing connection 0 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.

There seems to be an issue with the CA.

I changed the Repository URL from https to http - now it works.

Thank you

Martin

Am 11.08.22 um 13:35 schrieb Julio Gonzalez via Uyuni Users:

...

El jueves, 11 de agosto de 2022 13:20:28 (CEST) Martin via Uyuni Users escribió:

...

Hallo all

I can't connect to uyuni-stable repo:

uyuni:~ # zypper ref -s All services have been refreshed. Repository 'Update repository of openSUSE Backports' is up to date. Repository 'Non-OSS Repository' is up to date. Repository 'Haupt-Repository' is up to date. Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up to date. Repository 'Hauptaktualisierungs-Repository' is up to date. Repository 'Aktualisierungs-Repository (Nicht-Open-Source- Software)' is up to date. Retrieving repository 'uyuni-server-stable' metadata ................................................................. ........... ......................[error]   Repository 'uyuni-server-stable' is invalid. [uyuni-server- stable|https://download.opensuse.org/repositories/systemsmanag ement:/Uyuni:/Stable/images/repo/Uyuni-Server-POOL-x86_64- Media1/]   Valid metadata not found at specified URL History:    - [|] Error trying to read from ' https://download.opensuse.org/repositories/systemsmanagement:/Uyun i:/Stable /images/repo/Uyuni-Server-POOL-x86_64-Media1/'   - Download (curl) error for ' https://download.opensuse.org/repositories/systemsmanagement:/Uyun i:/Stable /images/repo/Uyuni-Server-POOL-x86_64-Media1/content':   Error code: Curl error 60      Error message: SSL certificate problem: unable to get local issuer certificate

Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'uyuni-server-stable' because of the above error. Some of the repositories have not been refreshed because of an error. curl -v https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable/images/repo/Uyuni-Server-POOL-x86_64- Media1/repodata/repomd.xml

and inspect the output

The repomd.xml doesn't get you redirected to a mirror, and works fine from here. But curl will give you more info about what's wrong.

In my case I see:

  Server certificate: *  subject: CN=opensuse.org *  start date: Jul 12 00:12:58 2022 GMT *  expire date: Oct 10 00:12:57 2022 GMT *  subjectAltName: host "download.opensuse.org" matched cert's "*.opensuse.org" *  issuer: C=US; O=Let's Encrypt; CN=R3 *  SSL certificate verify ok.

...

Two additional Questions

What I have to do, if the uyuni server IP has changed? AFAIK, as long as you keep the same hostname, you don't need to do anything.

If you also changed the hostname: https://www.uyuni-project.org/uyuni-docs/en/uyuni/administration/ troubleshooting/tshoot-hostname-rename.html

...

What I have to do, if the IP of a uyuni managed client has changed? AFAI; if you onboarded using the clients hostname (recommended), nothing particular. At some point a refresh will happen and you will see the new IPs at the UI.

But if you onboarded using the IP of the clients, then I think (but I am not sure), that you need to use reactivation keys.

https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/ activation-keys.html#_reactivation_keys

...

We move our servers to a new IP Range. As long as you are using hostnames in all cases, chaging IPs should not really big an issue

 

...

Best regards

Martin

Am 10.08.22 um 13:07 schrieb Julio Gonzalez via Uyuni Users:

...

VERY IMPORTANT: 2022.08 requires special procedures if you are not already using Uyuni 2022.06! The configuration files for the proxy on containers also   needs to be updated. Make sure you read the release notes before updating!>

We are happy to announce the availability of Uyuni 2022.08. Most openSUSE mirrors should already have 2022.08, but if you do not see it yet, wait a few   hours until your local openSUSE mirror is synced.

Athttps://www.uyuni-project.org/pages/stable-version.html  you will find all   the resources you need to start working with Uyuni 2022.08, including the release notes, documentation, requirements and setup instructions.>

This is the list of highlights for this release:

- Ubuntu 22.04 as client - GPG key handling in Uyuni - Disabling locally defined repositories - Technology Preview: Helm chart to deploy containerized Uyuni Proxy

    and Retail Branch Server

Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be   no maintenance of 2022.08

As always, we hope you will enjoy Uyuni 2022.08 and we invite everyone of you   to send us your feedback [1] and of course your patches, if you can contribute.

Happy hacking!

[1]https://www.uyuni-project.org/pages/contact.html

Hello Julio and Victor

The curl command say the certificate is ok, but zypper don't work.

I then removed the whole domain opensuse.org from the firewall TLS/SSL 
Inspection (not only download.opensuse.org) - and after that, it has 
worked with zypper also.

It's ok for me.

Best regards and many thank for help

Martin

Am 12.08.22 um 10:22 schrieb Julio Gonzalez via Uyuni Users:
> Or try with curl -k -v to inspect the output.
>
> -k forces the connection even if the SSL certification fails.
>
> El jueves, 11 de agosto de 2022 17:52:56 (CEST) Victor Zhestkov via Uyuni
> Users escribió:
>> Martin, could you please to check the output of the following command
>> also:
>>
>> echo | openssl s_client -connect download.opensuse.org:443
>>
>> Victor
>>
>> On Thu, 2022-08-11 at 17:50 +0200, Martin via Uyuni Users wrote:
>>
>>> Hello Julio
>>>
>>> uyuni:~ # curl -v
>>> https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stabl
>>> e/images/repo/Uyuni-Server-POOL-x86_64-Media1/repodata/repomd.xml
>   *
>>> Trying 195.135.221.134:443...
>>> * Connected to download.opensuse.org (195.135.221.134) port 443 (#0)
>>> * ALPN, offering h2
>>> * ALPN, offering http/1.1
>>> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
>>> * TLSv1.3 (IN), TLS handshake, Server hello (2):
>>> * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
>>> * TLSv1.3 (IN), TLS handshake, Certificate (11):
>>> * TLSv1.3 (OUT), TLS alert, unknown CA (560):
>>> * SSL certificate problem: unable to get local issuer certificate
>>> * Closing connection 0
>>> curl: (60) SSL certificate problem: unable to get local issuer
>>> certificate
>>> More details here: https://curl.se/docs/sslcerts.html
>>>
>>> curl failed to verify the legitimacy of the server and therefore
>>> could not
>>> establish a secure connection to it. To learn more about this
>>> situation and
>>> how to fix it, please visit the web page mentioned above.
>>>
>>> There seems to be an issue with the CA.
>>>
>>> I changed the Repository URL from https to http - now it works.
> Yes, that works but now your connection is not encrypted, so I'd strongly
> recommend you debug why you are having the issue.
>
> Besides the next major upgrade for Uyuni, next year, will restore the repos to
> https.
>
>
>>> Thank you
>>>
>>> Martin
>>>
>>>
>>> Am 11.08.22 um 13:35 schrieb Julio Gonzalez via Uyuni Users:
>>>
>>>> El jueves, 11 de agosto de 2022 13:20:28 (CEST) Martin via Uyuni
>>>> Users
>>>> escribió:
>>>>
>>>>> Hallo all
>>>>>
>>>>> I can't connect to uyuni-stable repo:
>>>>>
>>>>> uyuni:~ # zypper ref -s
>>>>> All services have been refreshed.
>>>>> Repository 'Update repository of openSUSE Backports' is up to
>>>>> date.
>>>>> Repository 'Non-OSS Repository' is up to date.
>>>>> Repository 'Haupt-Repository' is up to date.
>>>>> Repository 'Update repository with updates from SUSE Linux
>>>>> Enterprise
>>>>> 15' is up to date.
>>>>> Repository 'Hauptaktualisierungs-Repository' is up to date.
>>>>> Repository 'Aktualisierungs-Repository (Nicht-Open-Source-
>>>>> Software)' is
>>>>> up to date.
>>>>> Retrieving repository 'uyuni-server-stable' metadata
>>>>> .................................................................
>>>>> ...........
>>>>> ......................[error]
>>>>    Repository 'uyuni-server-stable' is invalid.
>>>>
>>>>> [uyuni-server-
>>>>> stable|https://download.opensuse.org/repositories/systemsmanag
>>>>> ement:/Uyuni:/Stable/images/repo/Uyuni-Server-POOL-x86_64-
>>>>> Media1/]
>>>>    Valid
>>>>
>>>>> metadata not found at specified URL
>>>>> History:
>>>>>     - [|] Error trying to read from
>>>>> '
>>>>> https://download.opensuse.org/repositories/systemsmanagement:/Uyun
>>>>> i:/Stable
>>>>> /images/repo/Uyuni-Server-POOL-x86_64-Media1/'
>>>>    - Download (curl) error for
>>>>
>>>>> '
>>>>> https://download.opensuse.org/repositories/systemsmanagement:/Uyun
>>>>> i:/Stable
>>>>> /images/repo/Uyuni-Server-POOL-x86_64-Media1/content':
>>>>    Error code: Curl
>>>>
>>>>> error 60
>>>>>       Error message: SSL certificate problem: unable to get local
>>>>> issuer
>>>>> certificate
>>>>>
>>>>> Please check if the URIs defined for this repository are pointing
>>>>> to a
>>>>> valid repository.
>>>>> Skipping repository 'uyuni-server-stable' because of the above
>>>>> error.
>>>>> Some of the repositories have not been refreshed because of an
>>>>> error.
>>>> curl -v
>>>> https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/
>>>> Stable/images/repo/Uyuni-Server-POOL-x86_64-
>>>> Media1/repodata/repomd.xml
>>>>
>>>> and inspect the output
>>>>
>>>> The repomd.xml doesn't get you redirected to a mirror, and works
>>>> fine from
>>>> here. But curl will give you more info about what's wrong.
>>>>
>>>> In my case I see:
>>>>
>>>>    Server certificate:
>>>> *  subject: CN=opensuse.org
>>>> *  start date: Jul 12 00:12:58 2022 GMT
>>>> *  expire date: Oct 10 00:12:57 2022 GMT
>>>> *  subjectAltName: host "download.opensuse.org" matched cert's
>>>> "*.opensuse.org"
>>>> *  issuer: C=US; O=Let's Encrypt; CN=R3
>>>> *  SSL certificate verify ok.
>>>>
>>>>
>>>>> Two additional Questions
>>>>>
>>>>> What I have to do, if the uyuni server IP has changed?
>>>> AFAIK, as long as you keep the same hostname, you don't need to do
>>>> anything.
>>>>
>>>> If you also changed the hostname:
>>>> https://www.uyuni-project.org/uyuni-docs/en/uyuni/administration/
>>>> troubleshooting/tshoot-hostname-rename.html
>>>>
>>>>
>>>>> What I have to do, if the IP of a uyuni managed client has
>>>>> changed?
>>>> AFAI; if you onboarded using the clients hostname (recommended),
>>>> nothing
>>>> particular. At some point a refresh will happen and you will see
>>>> the new IPs
>>>> at the UI.
>>>>
>>>> But if you onboarded using the IP of the clients, then I think (but
>>>> I am not
>>>> sure), that you need to use reactivation keys.
>>>>
>>>> https://www.uyuni-project.org/uyuni-docs/en/uyuni/client-configuration/
>>>> activation-keys.html#_reactivation_keys
>>>>
>>>>
>>>>> We move our servers to a new IP Range.
>>>> As long as you are using hostnames in all cases, chaging IPs should
>>>> not really
>>>> big an issue
>>>>
>>>>    
>>>>
>>>>> Best regards
>>>>>
>>>>> Martin
>>>>>
>>>>> Am 10.08.22 um 13:07 schrieb Julio Gonzalez via Uyuni Users:
>>>>>
>>>>>
>>>>>> VERY IMPORTANT: 2022.08 requires special procedures if you are
>>>>>> not
>>>>>> already
>>>>>> using Uyuni 2022.06! The configuration files for the proxy on
>>>>>> containers
>>>>>> also
>>>>    needs to be updated. Make sure you read the release notes before
>>>>
>>>>>> updating!>
>>>>>>
>>>>>>
>>>>>> We are happy to announce the availability of Uyuni 2022.08.
>>>>>> Most openSUSE
>>>>>> mirrors should already have 2022.08, but if you do not see it
>>>>>> yet, wait a
>>>>>> few
>>>>    hours until your local openSUSE mirror is synced.
>>>>
>>>>>>
>>>>>> Athttps://www.uyuni-project.org/pages/stable-version.html  you
>>>>>> will find
>>>>>> all
>>>>    the resources you need to start working with Uyuni 2022.08,
>>>>
>>>>>> including the release notes, documentation, requirements and
>>>>>> setup
>>>>>> instructions.>
>>>>>>
>>>>>>
>>>>>> This is the list of highlights for this release:
>>>>>>
>>>>>>
>>>>>>
>>>>>> - Ubuntu 22.04 as client
>>>>>> - GPG key handling in Uyuni
>>>>>> - Disabling locally defined repositories
>>>>>> - Technology Preview: Helm chart to deploy containerized Uyuni
>>>>>> Proxy
>>>>>>
>>>>>>      and Retail Branch Server
>>>>>>
>>>>>>
>>>>>>
>>>>>> Remember that Uyuni will follow a rolling release planning, so
>>>>>> the next
>>>>>> version will contain bugfixes for this one and any new
>>>>>> features. There
>>>>>> will be
>>>>    no maintenance of 2022.08
>>>>
>>>>>>
>>>>>> As always, we hope you will enjoy Uyuni 2022.08 and we invite
>>>>>> everyone of
>>>>>> you
>>>>    to send us your feedback [1] and of course your patches, if you
>>>> can
>>>>
>>>>>> contribute.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Happy hacking!
>>>>>>
>>>>>>
>>>>>>
>>>>>> [1]https://www.uyuni-project.org/pages/contact.html
>>>>
>>
>