Bug 174797 - osad stops working when system is reregistered with Satellite
osad stops working when system is reregistered with Satellite
Status: CLOSED DUPLICATE of bug 185476
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Todd Sanders
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2005-12-02 06:19 EST by Carsten Clasohm
Modified: 2008-07-29 12:12 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-29 12:12:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Carsten Clasohm 2005-12-02 06:19:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

Description of problem:
When you install osad on a system, it stores authentication information in /etc/sysconfig/rhn/osad-auth.conf. This file is not updated when the system is deleted on the Satellite Server and reregistered. Afterwards, osad will not print any error messages, but does not pick up any actions from the Satellite any more.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Register a system with a Satellite server.
2. Install and start the osad service.
3. Trigger an action on the Satellite and verify that it gets picked up by the client system.
4. Delete the system on the Satellite server.
5. Reregister the system with rhnreg_ks.
6. Optionally, restart the osad service.

Actual Results:  When you now trigger an action on the Satellite server, it will stay in pending state and will not be picked up by the client. No error messages are printed or logged on the client.

If you set debug_level to 1 in /etc/sysconfig/rhn/osad.conf, you will see the following in /var/log/osad:

2005-12-02 10:35:45 osad_client._check_signature: Signatures do not match 52e52edd2081462d02047b677e9f23491b85c15c ed877e96509610e92c6962dd679f818bc2e3fa7d
2005-12-02 10:35:45 jabber_lib._check_signature_from_message: Mismatching signatures
2005-12-02 10:35:49 jabber_lib.__init__: 
2005-12-02 10:35:49 jabber_lib.jabber_join: Connected to jabber server linin.vfl
2005-12-02 10:35:54 jabber_lib._presence_callback: osad-87d5c990dd@linin.vfl/osad rhn-dispatcher-sat@linin.vfl/superclient
2005-12-02 10:35:59 osad_client._check_signature: Signatures do not match 536331b03abc8663b2723f2d65801532e0e05856 ee83beca4ee06fdd41d136101f5e3ffb4bc40fa0
2005-12-02 10:35:59 jabber_lib._check_signature_from_message: Mismatching signatures
2005-12-02 10:36:04 osad_client._check_signature: Signatures do not match 8d93ebb0a852182b5b860d0d45f270b3914bb002 e0f069761f532496d2d4d72f11cd120c3399f67a
2005-12-02 10:36:04 jabber_lib._check_signature_from_message: Mismatching signatures

Only when you delete /etc/sysconfig/rhn/osad-auth.conf and restart the osad service are actions from the Satellite picked up again.

Expected Results:  When osad starts, it should automatically check if osad-auth.conf needs to be recreated, and do this.

At a minimum, it should fail to start and log something when osad-auth.conf is invalid. Right now, you first have to set the debug level to 1 to get any information, and the information you get is not too helpful.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.