octo-diff: on scheduler nodes (saatchi, scheduler0.staging), the period is increased
accordingly:
```
*******************************************
Systemd::Timer[swh-scheduler-update-metrics.timer] =>
parameters =>
timer_content =>
@@ -3,56 +3,5 @@7 @@
_
[Timer]
-OnCalendar=daily
+OnCalendar=*-*-* 00,04,08,12,16,20,24:00:00
Unit=swh-scheduler-update-metrics.service
+OnCalendar=00/4:00
+RandomizedDelaySec=1h
_
[Unit]
*******************************************
Systemd::Unit_file[swh-scheduler-update-metrics.timer] =>
parameters =>
content =>
@@ -3,56 +3,5 @@7 @@
_
[Timer]
-OnCalendar=daily
+OnCalendar=*-*-* 00,04,08,12,16,20,24:00:00
Unit=swh-scheduler-update-metrics.service
+OnCalendar=00/4:00
+RandomizedDelaySec=1h
_
[Unit]
*******************************************
```
PatchingOn a scheduler0.staging vm with the following ^ applied, it's ok with that new setup:restarting the timer manually makes the
next trigger roughly be around the 4h (without being exactly rounded):
```
root@scheduler0:~# datesystemctl status swh-scheduler-update-metrics.timer | grep "Trigger:"
Trigger: Mon 2021-08-30 16:48:44 UTC; 4h 17min left
Mon 30 Aug 2021 10:17:20 AM UTCroot@scheduler0:~# systemctl restart swh-scheduler-update-metrics.timer
root@scheduler0:~# systemctl status swh-scheduler-update-metrics.timer | grep -i t"Trigger:"
Trigger: Mon 2021-08-30 12:00:006:06:27 UTC; 1h 423h 35min left
Triggers: ● swh-scheduler-update-metrics.serviceroot@scheduler0:~# systemctl restart swh-scheduler-update-metrics.timer
root@scheduler0:~# systemctl status swh-scheduler-update-metrics.timer | grep "Trigger:"
Trigger: Mon 2021-08-30 16:56:40 UTC; 4h 25min left
```