https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-04-27T22:24:54ZPulpPulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=37632015-04-27T22:24:54Zrbarlow
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/3763/diff?detail_id=3024">diff</a>)</li></ul><p>Here is some more information I gathered about this. I updated the schedule again to be a few minutes in the future:</p>
<pre><code>$ pulp-admin rpm repo sync schedules update --repo-id zoo --schedule-id 553be0de7517d40591882021 --schedule 2015-04-27T22:20:00Z/P1D
Successfully updated schedule
</code></pre>
<p>Then I configured celerybeat to run in Debug logging, and saw this:</p>
<pre><code>Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: root:DEBUG: one or more enabled schedules has been updated
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.async.scheduler:DEBUG: loading schedules from app
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.async.scheduler:DEBUG: loading schedules from DB
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.async.scheduler:DEBUG: loaded 2 schedules
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.db.model.dispatch:DEBUG: not running task 553eaee47517d419c494b574: 84931 seconds remaining
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.db.model.dispatch:DEBUG: not running task 553be0de7517d40591882021: 73831 seconds remaining
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: pulp.server.async.worker_watcher:DEBUG: received 'scheduler-event' from scheduler@cloud-basebox.localdomain at time: 2015-04-27 22:17:28.973679
Apr 27 22:17:28 cloud-basebox.localdomain pulp[6978]: celery.beat:DEBUG: beat: Waking up in 1.50 minutes.
</code></pre>
<p>Note that the scheduler saw the change at 22:17, which was before the next run at 22:20. However, note that it still thinks the next run for that schedule is 73,831 seconds away rather than ~2.5 minutes.</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=37782015-04-28T14:48:42Zbmbouterbmbouter@redhat.com
<ul></ul><p>Is it possible this is related to <a class="issue tracker-1 status-11 priority-6 priority-default closed" title="Issue: Updating a sync plan's frequency does not seem to affect future syncs (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/516">#516</a>?</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=37942015-04-28T16:49:16Zrbarlow
<ul></ul><p>On 04/28/2015 10:48 AM, bmbouter wrote:</p>
<blockquote>
<p>Is it possible this is related to <a class="issue tracker-1 status-11 priority-6 priority-default closed" title="Issue: Updating a sync plan's frequency does not seem to affect future syncs (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/516">#516</a> <<a href="https://pulp.plan.io/issues/516" class="external">https://pulp.plan.io/issues/516</a>>?</p>
</blockquote>
<p>It is possible, though I'm not certain at this point. I didn't try to<br>
adjust the frequency, but instead I tried to update the start time. That<br>
bug seems to be about adjusting the frequency, so it may or may not be<br>
the same. It's worth looking into, thanks for the pointer!</p>
<p>--<br>
Randy Barlow</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=39072015-05-04T15:55:21Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Severity</strong> changed from <i>2. Medium</i> to <i>3. High</i></li><li><strong>Version</strong> set to <i>Master</i></li><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>Investigate whether this affects 2.6.</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=40872015-05-05T15:59:24Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>bmbouter</i></li></ul> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=43962015-05-18T13:59:55Zbmbouterbmbouter@redhat.com
<ul><li><strong>Subject</strong> changed from <i>If a sync schedule is updated to change the time it runs, the scheduler does not run it at the new start time</i> to <i>If a sync, publish, or consumer schedules are updated to change the time it runs, the celerybeat does not run it at the new start time</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/4396/diff?detail_id=3879">diff</a>)</li></ul><p>QE to verify this, please do the following.</p>
<p>0) Install a fully working version of Pulp and start it up<br>
1) Create a zoo repo<br>
2) Create a sync schedule for zoo that will sync very far in the future (ie: a date in 2016)<br>
3) List that sync and verify it got created<br>
4) Update the sync with pulp-admin to have it run a few minutes in the future (at least 120 seconds from the time you issue the command)<br>
5) Verify that the sync runs at the new time you specified<br>
6) Do the same steps 2-5 for a publish schedule and verify that<br>
7) Install a consumer<br>
8) Do steps 2-5 only with a consumer action and verify that type of schedule also updates.</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=43972015-05-18T14:37:26Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p>PR available at: <a href="https://github.com/pulp/pulp/pull/1861" class="external">https://github.com/pulp/pulp/pull/1861</a></p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=43982015-05-18T14:38:09Zbmbouterbmbouter@redhat.com
<ul><li><strong>Subject</strong> changed from <i>If a sync, publish, or consumer schedules are updated to change the time it runs, the celerybeat does not run it at the new start time</i> to <i>If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start time</i></li></ul> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=44062015-05-18T17:16:53Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Updates to schedules are now respected by celerybeat The schedule field was being updated, but n..." href="https://pulp.plan.io/projects/pulp/repository/pulp/revisions/472b84cb765490752a0aef21147abecee7830b23">pulp|472b84cb765490752a0aef21147abecee7830b23</a>.</p> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=44072015-05-18T17:31:35Zbmbouterbmbouter@redhat.com
<ul><li><strong>Platform Release</strong> set to <i>2.6.2</i></li></ul> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=44222015-05-19T00:00:33Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=44452015-05-20T15:32:53Zpthomas@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>6</i></li></ul><p>verified<br>
[root@mgmt12 ~]# rpm -qa pulp-server<br>
pulp-server-2.6.2-0.2.beta.el6.noarch<br>
[root@mgmt12 ~]#<br>
1. verified sync update works as expected<br>
2. also verified consumer install schedule work</p>
<pre><code>[root@mgmt12 ~]# pulp-admin rpm consumer package install schedules create --consumer-id patch --schedule 2016-04-27T22:20:00Z/P1D -n dog
Schedule successfully created
[root@mgmt12 ~]#
[root@mgmt12 ~]#
[root@mgmt12 ~]# pulp-admin rpm consumer package install schedules list --consumer-id patch
+----------------------------------------------------------------------+
Schedules
+----------------------------------------------------------------------+
Schedule: 2015-05-20T15:05:00Z/P1D
Id: 555c9d62e8ec9860dcbdcadb
Enabled: True
Next Run: 2015-05-21T15:05:00Z
Schedule: 2016-04-27T22:20:00Z/P1D
Id: 555ca3b3e8ec9860dbfe47fa
Enabled: True
Next Run: 2016-04-27T22:20:00Z
[root@mgmt12 ~]# pulp-admin rpm consumer package install schedules update --consumer-id patch --schedule-id 555ca3b3e8ec9860dbfe47fa -s 2015-05-20T15:15:00Z/P1D
Successfully updated schedule
[root@mgmt12 ~]# pulp-admin rpm consumer package install schedules list --consumer-id patch
+----------------------------------------------------------------------+
Schedules
+----------------------------------------------------------------------+
Schedule: 2015-05-20T15:05:00Z/P1D
Id: 555c9d62e8ec9860dcbdcadb
Enabled: True
Next Run: 2015-05-21T15:05:00Z
Schedule: 2015-05-20T15:15:00Z/P1D
Id: 555ca3b3e8ec9860dbfe47fa
Enabled: True
Next Run: 2015-05-20T15:15:00Z
<\pre>
</code></pre> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=61302015-09-14T12:52:17Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>6</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #922: If a sync, publish, or consumer schedule is updated to change the time it runs, celerybeat does not run it at the new start timehttps://pulp.plan.io/issues/922?journal_id=398892019-04-15T20:50:09Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>