Bug 517252

Description of problem:
If a kickstart is scheduled over 4hours in advance, it fails. The same kickstart finishes successfully, if running immediately (not postponed).

Version-Release number of selected component (if applicable):
Satellite-5.3.0-RHEL5-re20090730.0

How reproducible:
always, I reproduced it 5times with different clients

Steps to Reproduce:
1. create new kickstart profile (ks-rhel-i386-server-5-u3 tree, no virtualization)
2. register a i386 client, add Provisioning entitlement, start osad
3. schedule a kickstart with option "Begin kickstart at the next system check in" and make sure, the kickstart finishes successfully and the client is capable of this type of kickstart
6. schedule the same kickstart for the same client with checked option "Schedule kickstart no sooner than:" and set time (current time + 4h15m)

Actual results:
Kickstart fails.
From client remote console:
--------------------------------------------------------------------------------
loader received SIGSEGV!  Backtrace:                                           
[0x8048cf4]
[0xfa9420]
[0x817ebf3]
[0x806254c]
[0x806bb7b]
[0x806bcb6]
[0x806c167]
[0x806b59e]
[0x80618dc]
[0x8062019]
install exited abnormally [1/1] 
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
 /proc/bus/usb done
 /proc done
 /dev/pts done
 /sys done
 /tmp/ramfs done
you may safely reboot your system
--------------------------------------------------------------------------------

on webui I see successfully finished:
* System reboot scheduled by admin  08/10/09 11:00:56 PM 
* Initiate a kickstart scheduled by admin  08/10/09 11:00:54 PM 
* Package Install scheduled by admin  08/10/09 11:00:28 PM 

Expected results:
The client will be kickstarted successfully, when it's scheduled over night or over weekend.

Additional info:
Bug discovered, when validating BZ#489736.