[Spacewalk-list] wrong schedule times

[Paul Robert Marino]

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.
On Jul 6, 2012 2:50 AM, "Yura Demchenko" <demchenko.ya at gmail.com> wrote:

> 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
> Spacewalk-list at redhat.com
> https://www.redhat.com/**mailman/listinfo/spacewalk-**list<https://www.redhat.com/mailman/listinfo/spacewalk-list>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120706/cf20fcbe/attachment.htm>