Closed Bug 1013256 Opened 12 years ago Closed 11 years ago

[ReMo] Update reps.mozilla.org cron jobs (extend_voting_period, poll_vote_reminder)

Categories

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: giorgos, Assigned: cturra)

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/701] )

Please add to remo production (reps.mozilla.org) the following cron jobs if they don't already exist ./manage.py cron extend_voting_period ./manage.py cron poll_vote_reminder and list all the cronjobs we currently have.
the cron for poll_vote_reminder was present on dev only. i have added extend_voting_period there also for testing. once you're happy with it, we can promote these to stage. currently, these are the crons for all the reps environments: # Dev site jobs */5 * * * * root /usr/bin/flock -w 10 /var/lock/reps-dev /data/genericrhel6-dev/src/reps-dev.allizom.org/update 2&>1 > /dev/null 2,12,22,32,42,52 * * * * root /usr/bin/flock -w 10 /var/lock/reps-dev-bugs /data/genericrhel6-dev/src/reps-dev.allizom.org/remo/manage.py fetch_bugs 2&>1 > /dev/null 12 * * * * * root /usr/bin/flock -w 10 /var/lock/reps-dev-vote /data/genericrhel6-dev/src/reps-dev.allizom.org/remo/manage.py cron poll_vote_reminder 2&>1 > /dev/null 22 * * * * * root /usr/bin/flock -w 10 /var/lock/reps-dev-poll /data/genericrhel6-dev/src/reps-dev.allizom.org/remo/manage.py cron extend_voting_period 2&>1 > /dev/null # Stage site jobs 0 0 * * 0 root /usr/bin/flock -w 10 /var/lock/reps-stage /data/genericrhel6-stage/src/reps.allizom.org/remo/manage.py update_product_details 2&>1 > /dev/null # Prod site jobs 15 0 * * 0 root /usr/bin/flock -w 10 /var/lock/reps-prod /data/genericrhel6/src/reps.mozilla.org/remo/manage.py update_product_details 2&>1 > /dev/null 8,18,28,38,48,58 * * * * root /usr/bin/flock -w 10 /var/lock/reps-prod-bugs /data/genericrhel6/src/reps.mozilla.org/remo/manage.py fetch_bugs > /data/genericrhel6/src/reps.mozilla.org/remo/media/fetch_bugs.log 2>&1 1 0 1 * * root /usr/bin/flock -w 10 /var/lock/reps-prod-no5 /data/genericrhel6/src/reps.mozilla.org/remo/manage.py cron new_reps_reminder 2&>1 > /dev/null
Assignee: server-ops-webops → cturra
Flags: needinfo?(giorgos)
Looks good, please proceed to stage.
Flags: needinfo?(giorgos)
these have been added to stage also. please let me know when you want this rolled into production. $ svn diff svn Index: modules/webapp/files/genericrhel6/admin/etc-cron.d/reps.mozilla.org =================================================================== --- modules/webapp/files/genericrhel6/admin/etc-cron.d/reps.mozilla.org (revision 87798) +++ modules/webapp/files/genericrhel6/admin/etc-cron.d/reps.mozilla.org (working copy) @@ -9,7 +9,8 @@ # Stage site jobs 0 0 * * 0 root /usr/bin/flock -w 10 /var/lock/reps-stage /data/genericrhel6-stage/src/reps.allizom.org/remo/manage.py update_product_details 2&>1 > /dev/null -#5,15,25,35,45,55 * * * * root /usr/bin/flock -w 10 /var/lock/reps-stage-bugs /data/genericrhel6-stage/src/reps.allizom.org/remo/manage.py fetch_bugs 2&>1 > /dev/null +32 * * * * * root /usr/bin/flock -w 10 /var/lock/reps-stage-vote /data/genericrhel6-stage/src/reps.allizom.org/remo/manage.py cron poll_vote_reminder 2&>1 > /dev/null +42 * * * * * root /usr/bin/flock -w 10 /var/lock/reps-stage-poll /data/genericrhel6-stage/src/reps.allizom.org/remo/manage.py cron extend_voting_period 2&>1 > /dev/null # Prod site jobs 15 0 * * 0 root /usr/bin/flock -w 10 /var/lock/reps-prod /data/genericrhel6/src/reps.mozilla.org/remo/manage.py update_product_details 2&>1 > /dev/null
Flags: needinfo?(giorgos)
Please proceed to prod. Thanks!
Flags: needinfo?(giorgos)
this has been pushed to prod as requested :)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Hi, I am reopening this bug because we migrated those cron jobs to celery. Can you please remove: * poll_vote_reminder * extend_voting_period from all of our deployments: * reps-dev.allizom.org * reps.allizom.org * reps.mozilla.org Also it would be really helpful for us to have a list of the crontab in each deployment to see what's left as a cron job. Thank you!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/701]
these crons have been removed as requested.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.