Hide Forgot
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): 5.0.1 How reproducible: Always 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.
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?