AFAIK the SLE instances do not trust the Packagehub by default. So I think you need something similar to: https://www.uyuni-project.org/uyuni-docs/uyuni/client-configuration/clients-... If I am not wrong, the key from PackageHub should be uploaded to /srv/www/ htdocs/pub @doc team, shouldn't we describe how to trust GPG keys for third party repositories at the clients? I can't see it at https://www.uyuni-project.org/ uyuni-docs/uyuni/administration/custom-channels.html On viernes, 24 de abril de 2020 14:40:36 (CEST) Tobias Crefeld wrote:
Hi,
I created a new SLES15-machine with a minimal setup and tried to add it to Uyuni using the "Bootstrapping" function at the WebGUI.
Initially it stopped after creating a Salt key but without any error message on the Uyuni-server and obviously without any deoployment on Uyuni or on the client.
It turned out that the resolv.conf was missing on the client and so the client wasn't able to start a connection to the Uyuni-server.
After creation of the resolv.conf the bootstrapping / registration process automatically continued, including "Apply states" (channels, packages, etc.) - everything seemed fine now.
But during installation of the pre-defined package list an error occured during the installation of one package. A manual installation using zypper install fails with the same message:
htop-2.2.0-bp150.2.4.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 65176565: NOKEY htop-2.2.0-bp150.2.4.x86_64 (SUSE-PackageHub-15-Standard-Pool for x86_64): Signature verification failed [4-Signatures public key is not available]
The repository list looks fine:
# zypper lr |egrep '(Standard|Alias)' # | Alias | Name | Enabled | GPG Check | Refresh 13 | susemanager:suse-packagehub-15-x86_64 | SUSE-PackageHub-15-Standard-Pool for x86_64 | Yes | ( p) Yes | Yes
Installation of the same package is no problem on other salt-clients using the same channel.
Any idea how to fix this (automatically)?
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com