Am Fri, 24 Apr 2020 15:46:20 +0200 schrieb Julio González Gil <jgonzalez@suse.com>:
AFAIK the SLE instances do not trust the Packagehub by default.
Thanks for the hint - seems that you're right! I checked the GPG-keys rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}\t%{SUMMARY}\n' and found an additional key gpg-pubkey-65176565 gpg(openSUSE:Backports OBS Project <openSUSE:Backports@build.opensuse.org>) on the "old" SLES15 systems. "Backports" is the forerunner of PackageHub, according to their homepage. During manual installation from an repository with an unknown key you usually get a dialogue if you want to import the key. This is of course no strategy for an auto deployment.
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
Haven't fully understood this advice as yet but I keep trying.
@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
Actually my expectation is that a channel that is provided via "Admin / Setup Wizard / Products" redistributes the respective GPG-key as well. Writing this I remember that I already had some problems with this channel earlier during the initial setup of Uyuni. The resolution was a manual call spacewalk-repo-sync -c suse-packagehub-15-x86_64 with an dialogue if I want to import the GPG-key. -- Gruss, Tobias Crefeld. xmpp (no email): crefeld@xabber.de -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org