[Spacewalk-list] package update issues

[James Hogarth]

On 2 February 2010 16:52, Kennedy, Ryan <rkennedy at paml.com> wrote:
> James, thanks for the reply.
>
> I checked and the client had the RPM-GPG-KEY-CentOS-5 key (i.e. E8562897) in /etc/pki/rpm-gpg which is the one yum was complaining about not having.  I ran a `rpm --import` on that key and tried it again and it worked great.  I am even able to push out a package update from the Spacewalk server now which is great.  There is only 1 other key in that directory though (RPM-GPG-KEY-beta) and the Spacewalk server has keys in that same directory for each repo that I have on it (EPEL, RPMForge, Updates, Spacewalk, etc.)  The key files are... (RPM-GPG-KEY-dag   RPM-GPG-KEY-redhat-former   RPM-GPG-KEY-redhat-rhz RPM-GPG-KEY-CentOS-5  RPM-GPG-KEY-EPEL  RPM-GPG-KEY-redhat-release  RPM-GPG-KEY-spacewalk).
>
> My question is: Do I need to add all of those keys to the kickstart profile (I would assume yes at least for EPEL and RPMForge)?  How do I add them? Under "Kickstart::GPG and SSL keys" perhaps, and then check them off in "KS Profile::System Details::GPG & SSL"?  Or do I add them under "KS Profile::Activation Keys".  I apologize if this is common knowledge.  This is all pretty new to me and the CentOS Spacewalk guide didn't cover adding keys to the KS profile.
> Thanks.
>
> --Ryan
>
Systems/Kickstart/GPG and SSL keys
Import your keys there...

Systems/Kickstart/Profiles
Go into your profile for your kickstart and in the GPG/SSL tab (under
system details)  tick the GPG keys and SSL certs you want imported.

Now newly kickstarted systems will have the GPG key imported.

If you view the kickstart file itself you can see what commands it
runs (basically echos the raw GPG to a /tmp file and imports it).

For existing systems you will need to import the file manually.

That at least is my implementation experience so far :)

James