Well that would seem to be a client bug. The as soon as possible is executed the next time the client checks in. I am curious thoug I know this shouldn't make a diference but is the time correct on both servers and are they in the same timezone? Additionally I simple workarond would be to manually run rhncheck on the client. <div class="gmail_quote">On Jul 6, 2012 2:50 AM, "Yura Demchenko" <<a href="mailto:demchenko.ya@gmail.com">demchenko.ya@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi, I'm using spacewalk 1.7 with postgres and have weird problem with scheduler: when i schedule some action or package install by selecting "schedule as soon as possible" it places action in schedule in 8 hours in future. for example: i want to run remote command, on confirm page it shows correct current time in both "current spacewalk time" and "schedule action for no sooner then" (07/06/12 10:21 AM MSK), i select "schedule as soon as possible" and confirm. But when i review information about this action in scheduler it shows "earliest execution" 8 hours in future (07/06/2012 6:21 PM MSK). And indeed, action wouldn't happen before that time. However, if i select "schedule action for no sooner than" and pick some date in the past (1-2 days ago) - then action applies immediately. How can i fix this? SW server and clients have same system TZ ("europe/moscow"), same in "locale preferences". Latest timezone packages available applied to server and clients. -- Yura Demchenko _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote></div>