Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 590608 - re registering clients breaks OSAD auth
re registering clients breaks OSAD auth
Product: Spacewalk
Classification: Community
Component: Server (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Milan Zázrivec
Red Hat Satellite QA List
Depends On:
Blocks: space14
  Show dependency treegraph
Reported: 2010-05-10 06:09 EDT by Christoph Maser
Modified: 2011-04-26 05:10 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-04-26 05:10:42 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 Christoph Maser 2010-05-10 06:09:52 EDT
Description of problem:
if one re registers a client with rhnreg_ks the osad client auth gets invalid. to get osad to work correctly again one has to remove /etc/sysconfig/rhn/osad-auth.conf and restart osad on the client

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

How reproducible:
osad 0:5.9.31-1.el5.noarch

Steps to Reproduce:
1. register clietn with rhnreg_ks
2. configure and run osad
3. re-register clietn with rhnreg_ks
Actual results:
osad is running but does not pick up any scheduled actions, enabling debug logs shows it can not correctly authenticate

Expected results:
osad should run and pick up scheduled actions. a fix could be that rhnreg_ks resets osad authentication when needed.

Additional info:
Comment 1 Jan Pazdziora 2010-11-19 11:03:35 EST
Mass-moving to space13.
Comment 2 Milan Zázrivec 2011-02-03 12:26:45 EST
spacewalk.git master:

commit 5d7cbc0e2ac44b69c6dd8ed652bd85f572e95ef9
Author: Milan Zazrivec <mzazrivec@redhat.com>
Date:   Thu Feb 3 18:13:36 2011 +0100

    590608 - nullify jabber_ids from previous registrations
    This fix is to ensure push functionality will be functional after
    system's re-registration.
    Couple of things adding to the problem:
    * after system re-registration, systemid changes, jabber_id stays
    * rhnPushClient table with multiple rows with identical jabber_id
      and different server_id
    * osa-dispatcher tries to find shared key for given jabber_id, backend
      simply returns the first row fetched (now with an invalid shared key)
    * signatures computed by osad and osa-dispatcher do not match -> osad
      won't do anything
    * deleting the older servers in webui won't help

The fix for the described problem landed in spacewalk-backend (server
side component) and won't require any changes on client side (osad
should work automatically).

Thank you for your bug report, sorry for the delayed fix.
Comment 3 Milan Zázrivec 2011-02-04 05:15:52 EST
spacewalk.git SPACEWALK-1.3: 62e63a633b29d169c6c4524be248bfdf01b2e2b1
Comment 4 Miroslav Suchý 2011-04-11 03:45:14 EDT
Mass moving to ON_QA before release of Spacewalk 1.4
Comment 5 Miroslav Suchý 2011-04-26 05:10:42 EDT
Spacewalk 1.4 has been released

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