Per standard operating procedures for deploys/updates to production we should set the daily l10nupdate runs to happen only on Mon-Thurs.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Run l10nupdate monday to thursday | operations/puppet | production | +1 -0 |
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 350749 had a related patch set uploaded (by Reedy; owner: Reedy):
[operations/puppet@production] Run l10nupdate monday to thursday
Comment Actions
Not fussed either way, just it could be interpreted as either..
Friday 2am UTC SFers would be just about. Monday it would be Sunday evening...
Comment Actions
Idea was Sunday evening SF time is a few hours before EU Ops/RelEng wake up, so that's OK. And then stop Wednesday evening (SF) to not have l10n break on Friday morning (UTC)/Thursday evening (SF).
Comment Actions
Change 350749 merged by Dzahn:
[operations/puppet@production] Run l10nupdate monday to thursday
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2017-06-21T00:06:24Z] <mutante> tin (deployment): manually remove l10nupdate cron, let puppet re-create it after gerrit:350749. stops l10nupdate cron from running on weekends. naos didn't need an action. (T164035).
Comment Actions
[tin:~] $ sudo crontab -u l10nupdate -l | tail -2 # Puppet Name: l10nupdate 0 2 * * 1,2,3,4 /usr/local/bin/l10nupdate-1 --verbose >> /var/log/l10nupdatelog/l10nupdate.log 2>&1 [naos:~] $ sudo crontab -u l10nupdate -l | tail -2 # HEADER: not be deleted, as doing so could cause duplicate cron jobs.