Red Hat Bugzilla – Bug 808162
Kickstart created on satellite v 5.3 does not have step to import rpm gpg key.
Last modified: 2012-11-01 12:19:17 EDT
+++ This bug was initially created as a clone of Bug #708358 +++
Description of problem:
Systems installed from the kickstart created on spacewalk do not have the rpm gpg key imported.
Steps to Reproduce:
1. Login to spacewalk WebUI
2. Create kickstart profile for RHEL 5
3. Check the kickstart file or install a system using this kickstart and check output of
# rpm -qa | grep gpg
Kickstart file does not contain command to import GPG key.
kickstart installation from spacewalk should import the RHEL rpm gpg key by default.
Obviously there are many different operating systems that you can install from spacewalk, and each one has their own name for the RPM-GPG-KEY. The desire here is for RHEL kickstarts specifically to auto-import the GPG key, so that's what I've implemented. The code I added will import the RHEL RPM-GPG-KEY if it exists and do nothing if it does not, so this change shouldn't mess up other operating systems.
I briefly considered importing all GPG keys in /etc/pki/rpm-gpg/, but that's not very secure and there's really no guarantee that other operating systems will put there GPG keys there anyway.
Committed to Spacewalk master: 091f0d2410436170f304d8bd25639f6dbbcac35d
Marcelo provided fix to the fix in bug 816445, committed as
Moving ON_QA. Packages that address this bugzilla should now be available in yum repos at http://yum.spacewalkproject.org/nightly/
Spacewalk 1.8 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes18