[rhn-satellite-beta-users] Satellite 5 Beta and new RHEL5 GA

[Clifford Perry]

RHN Satellite 5.0 Beta was written last year and released just after 
RHEL 5 Beta 2 went public. As such the code base used the RHEL 5 Beta 2 
path for the 'RPM-GPG-KEY', which changed for RHEL 5 GA. So, the bug is 
real, and nothing you can do to fix it really. You can create a manual 
post script to import the right file for the Beta Satellite product. 
This is fixed in 4.2 Satellite and will also be fixed in the RHN 5.0 Sat 
GA version when released.

[root at dhcp231-182 rpm-gpg]# pwd
/etc/pki/rpm-gpg
[root at dhcp231-182 rpm-gpg]# ls
RPM-GPG-KEY-fedora            RPM-GPG-KEY-redhat-beta
RPM-GPG-KEY-fedora-test       RPM-GPG-KEY-redhat-former
RPM-GPG-KEY-redhat-auxiliary  RPM-GPG-KEY-redhat-release
[root at dhcp231-182 rpm-gpg]#


Something like:

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

Note, for RHEL 5 Red Hat changed the key used to sign RPMS. All RHEL 
2.1, 3 & 4 rpms are signed with the RPM-GPG-KEY-redhat-former key.

Cliff.


Kukrer, Koray wrote:
> I am having tough time to provision the RHEL5 GA thorough the new 
> satellite. I did not change anything but pointing the kickstart profile 
> and activation key to the new RHEL5 channel. I am having trouble to push 
> all the managed files when I use RHEL5 GA Channel. In the ks-post logs I 
> noticed this error; error: /etc/pki/rpm-gpg/RPM-GPG-KEY: import read failed
>  
> I believe it should not change from channel to channel. I am also 
> attaching the ks-post.log.  Can you guide me? 
>  
> Thanks,
>  
> Koray
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> rhn-satellite-beta-users mailing list
> rhn-satellite-beta-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-satellite-beta-users

-- 
Clifford Perry
Team Lead, Satellite Sustaining Engineering
Red Hat, Inc.
http://www.redhat.com/
+1 919 754 4403
RHCE# 803004507210710