This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 240
[2.7.0] Downtime recurrent #4071
Comments
+1 |
Can you try and say me if the 2.7.1 version fix the problem ? |
Thank you querwin, i'm testing update tomoro |
mtoufik
added a commit
that referenced
this issue
Jan 20, 2016
mtoufik
added a commit
that referenced
this issue
Jan 22, 2016
mtoufik
added a commit
that referenced
this issue
Jan 22, 2016
I think timezone are not apply and now timezone are created every time the cron is scheduled |
@ganoze : can you give us a status about this ticket ? Thanks |
Merci pour le fix, il corrige pas mal de bug. Exemple, j'ai un downtime de 19h à 7h avec deux plage 19:00 - 24:00 et 00:00 - 07:00 Pour contourner le problème je crée une première plage de 19:00 à 23:59 et une autre de 00:01 à 07:00 |
#4191 not merged ? |
kduret
added a commit
that referenced
this issue
Feb 18, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Les downtimes recurrent se basent sur l'heure UTC et non sur l'heure définit dans le champ Timezone (définit sur Administration ==> Parameters) ce qui fait qu'on se retrouve avec des downtimes récurrents qui sont décalés par rapport aux horaires définits
The text was updated successfully, but these errors were encountered: