Open albundy83 opened 9 years ago
Thanks for your question! The way I read the job configuration it's correct as you're explicitly defining the scheduleTimeZone
not the lastSuccess/Error
time zone. But for me it would make way more sense to have just a timezone configuration affection the whole job. I'll open a feature request for that.
Hello,
just to be sure I understand you, it's not possible to define time zone for lastSuccess/Error ? But I think also that the scheduleTimeZone should affect the whole job.
Thanks a lot.
@albundy83 As far as I know, there is actually no way to configure the lastSuccess/Error time zone.
Hello, not sure if it's an issue or a misunderstood on my side, but for my job, I have set : scheduleTimeZone to "Europe/Paris" (UTC+2). And when I saw the last lastSuccess time, it's set to UTC time (well, or at least with 2 hours late). Is it normal ? I'm under Debian 8.2 , using packages from repos.mesosphere : root@myserver:~# apt-cache policy chronos chronos:
Installed: 2.4.0-0.1.20151007110204.debian81
Candidate: 2.4.0-0.1.20151007110204.debian81 Version table:*** 2.4.0-0.1.20151007110204.debian81 0
500 http://repos.mesosphere.io/debian/ jessie/main amd64 Packages 100 /var/lib/dpkg/status