Red Hat Bugzilla – Bug 113947
rhn_check fails to update client
Last modified: 2009-11-13 11:07:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)
Description of problem:
rhn_check silently fails when it runs on a client that has been
registered using activation keys and has never used up2date.
This came to light when we were using kickstart to install the OS and
register the client. The client would then never accept updates.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Provision a client with OS (note client is registered with
satellite using activation key)
2. Schedule updates
3. run rhn_check on client
Actual Results: The update fails stating that the RH gpg key is not
installed on the client - note this error is on the satellite.
Expected Results: The scheduled packages should have been downloaded.
rhn_check does not install the RH gpg key if it is not already
installed. This should be the default since the above method -
provision, register with activation key, schedule updates - is the
method we are pushing with customers.
This is an rhn_check / up2date bug, sounds like.
you didnt include any version info, but I assume this
is for RHEL2.1?
Sorry about that - yes this is with the 2.1 version of satellite.
hmm, 2.1AS-u3 should automatically have the RH gpg keys
already added to the keyring (/etc/sysconfig/rhn/up2date-keyring.gpg)
what versions of rhn_register/up2date are you seeing
The CLIENTS we were installing were RHEL WS3.
I don't have them to hand but can find out the up2date (no
rhn_register) version if necssary but they should be whatever comes on
the WS3 install disks.
I belive this is fixed in more recent U3 releases, setting
to modified to have QA verify this.