You could use the Configuration Channel for this. But the Configuration Channel is kind of old and not very flexible. We use saltstack for key-distribution, but any other configuration-management-tool will do, like Ansible, Puppet, Chef, Saltstack or any of the likes.
Kind regards, Andreas Dijkman On 24 Jul 2020, at 20:09, Jackson K. Bonvissuto <jbonviss...@aplura.com<mailto:jbonviss...@aplura.com>> wrote: Hello all, I am trying to find a solution for populating GPG keys on client systems through Spacewalk, so that every time a system subscribes to a new channel and I do not have to wget the key manually. Are there any systems in spacewalk to auto distribute the channel's key when a client subscribes to it, or an alternate recommended solution. Example of the issue when installing a package from a new channel: yum install osquery-4.4.0-1.x86_64 Is this ok [y/d/N]: y #error Downloading packages: warning: /var/cache/yum/x86_64/7/osquery-x86_64/packages/osquery-4.4.0-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID c9d8b80b: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/OSQUERY-S3-RPM-REPO-GPGKEY GPG key retrieval failed: [Errno 14] curl#37 - "Couldn't open file /etc/pki/rpm-gpg/OSQUERY-S3-RPM-REPO-GPGKEY" Currently solved by manually placing the key in “/etc/pki/rpm-gpg on the client system. Thanks, Jackson _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com> https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
