Bug 428890 - osad doesn't seem to work unless restarted
Summary: osad doesn't seem to work unless restarted
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other
Version: 501
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Pradeep Kilambi
QA Contact: Brandon Perkins
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-15 21:26 UTC by Lana Akamine
Modified: 2008-09-24 19:53 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2008-09-24 19:53:49 UTC

Attachments (Terms of Use)

Description Dan Poler 2008-01-15 21:26:17 UTC
Description of problem:
Client is installing osad and chkconfig'ing it on during system provisioning
from kickstart. osad seems to not work (actions scheduled on the Sat server hang
until osad is restarted, but some amount of time must pass between when system
is first booted and osad is restarted for this to work.

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

How reproducible:

Steps to Reproduce:
1. Kickstart a system from Satellite. Have the kickstart use an activation key
that installs osad and a %post that does a chkconfig osad on.
2. Wait for system to reboot. When it does, use Satellite to schedule an action
(any action).  
3. Some time later, restart osad via service osad restart
Actual results:
The action scheduled in step #2 will remain pending until a normal rhnsd checkin

Expected results:
Because osad is running, it is expected that the action would complete quickly,
if not immediately.

Additional info:
If osad is restarted immediately after the box is booted, the same thing happens
-- no actions complete until a normal rhnsd checkin. However, if osad is
restarted after some time has passed, it will begin to function normally. No
idea how long must pass for this to happen. Once osad is restarted and this time
constraint is met, the pending actions will clear.
It seems that this osad restart must only happen once, and then the system is
forever fine, even across reboots.

Comment 1 Dan Poler 2008-01-15 22:43:44 UTC
The magic number seems to be about ten minutes - a system must be up for 10
minutes on its first boot, then have osad restarted, then henceforth it works. 

Does something happen to osad configuration-wise in the first 10 minutes that
would necessitate a restart before it functions correctly?

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