Bug 679353 - osad does not detect the system was re-registered
Summary: osad does not detect the system was re-registered
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Clients
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-02-22 11:03 UTC by Milan Zázrivec
Modified: 2011-12-22 16:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-22 16:50:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Milan Zázrivec 2011-02-22 11:03:03 UTC
Description of problem:
Unless you manually restart osad on the client system, osad is unable to detect
the system in question was re-registered.

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

How reproducible:
Always

Steps to Reproduce:
1. Register a client system to Spacewalk, osad running and working
2. Re-register the machine in question
3. Schedule an event (ping for example) for the re-registered system
  
Actual results:
osad won't detect the system was re-registered, actions scheduled
for the system won't be picked up.

Expected results:
osad is able to detect the system was re-registered.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=185476

Comment 1 Miroslav Suchý 2011-04-11 07:34:18 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 2 Miroslav Suchý 2011-04-11 07:37:29 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 3 Jan Pazdziora 2011-07-20 11:52:56 UTC
Aligning under space16.

Comment 4 Milan Zázrivec 2011-10-21 15:23:19 UTC
spacewalk.git master: df8fd7dddba65f55305454d4b32a53ee2fe59813

Comment 5 Milan Zázrivec 2011-12-22 16:50:50 UTC
Spacewalk 1.6 has been released.


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