Hi, I'm having a similar problem in Spacewalk 2.1.
My timezone is set to BST (British Summer Time, currently GMT+1) and when I schedule a System reboot to any hour PM it gets converted to the same hour AM, e.g.: * using the picker I schedule an event to 17:00 GMT (5 PM GMT) * using Events > Pending I can see my event is scheduled to 5:00:00 AM BST * on the database the event is schedule to 5:00:00 AM BST too: spaceschema=# select * from rhnaction order by created desc limit 1; id | org_id | action_type | name | scheduler | earliest_action | version | archived | prerequisite | created | modified ------+--------+-------------+---------------+-----------+------------------------+---------+----------+--------------+-------------------------------+------------------------------- 5370 | 1 | 9 | System reboot | 2 | 2014-04-04 05:00:00+01 | 2 | 0 | | 2014-04-03 11:19:34.501184+01 | 2014-04-03 11:19:34.501184+01 (1 row) So it seems the picker is doing a bad date conversion. 2014-04-01 12:22 GMT+01:00 Ron Helzer <[email protected]>: > > Hi Duncan, > > Most, if not all, other areas of Spacewalk display the correct timezone - > it's only the new date / time picker used to schedule actions where I'm > seeing the discrepancy. > > Just now, I tried scheduling a "Run arbitrary script" command. The > date/time picker only shows / allows EST. When I check pending events, I > see the action scheduled time displayed as EDT and offset one hour into the > future. > > Regards, > > - Ron - > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > -- Paulo Silva <[email protected]>
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
