Issue #516
closed
Updating a sync plan's frequency does not seem to affect future syncs
Description
Description of problem:
When updating a sync plan from hourly to daily, the 'next_run' times do not seem to update at all.
Version-Release number of selected component (if applicable):
2.4.1
How reproducible:
Always
Steps to Reproduce:
1. Create a schedule on a repo to sync every hour
2. Update the schedule to sync daily
Actual results:
Repo still appears to sync every hour
Expected results:
Repo starts syncing daily
Additional info:
Initially with a schedule of:
"2014-08-27T00:38:00Z/PT1H" I get a 'next_run' time of "2014-09-08T22:38:00Z"
Changing the schedule to:
"2014-08-27T00:38:00Z/PT24H" leaves the 'next_run' time at "2014-09-08T22:38:00Z"
Waiting a couple hours, its still scheduling hourly. next_run: "2014-09-09T01:38:00Z"
Even the next day: "2014-09-09T13:38:00Z"
+ This bug was cloned from Bugzilla Bug #1139703 +
Updated by mhrivnak over 8 years ago
I was able to reproduce this. I created the same schedule for a repo sync, and after it ran once, I did the same update from 1H to 24H. I then did a schedule list:
$ pulp-admin rpm repo sync schedules list --repo-id=zoo
--------------------------------------------------------------------
Schedules
--------------------------------------------------------------------
Schedule: 2014-08-27T00:38:00Z/PT24H
Id: 540f090a3de3a318ada71a76
Enabled: True
Next Run: 2014-09-09T14:38:00Z
Then I waited until after 14:38:00Z, and did another schedule list:
$ pulp-admin rpm repo sync schedules list --repo-id=zoo
--------------------------------------------------------------------
Schedules
--------------------------------------------------------------------
Schedule: 2014-08-27T00:38:00Z/PT24H
Id: 540f090a3de3a318ada71a76
Enabled: True
Next Run: 2014-09-09T15:38:00Z
The schedule is continuing to run hourly.
+ This comment was cloned from Bugzilla #1139703 comment 1 +
Updated by cduryee over 8 years ago
Moving back to NEW status for now.
+ This comment was cloned from Bugzilla #1139703 comment 2 +
Updated by cduryee over 8 years ago
picking BZ back up
+ This comment was cloned from Bugzilla #1139703 comment 3 +
Updated by cduryee over 8 years ago
https://github.com/pulp/pulp/pull/1170
+ This comment was cloned from Bugzilla #1139703 comment 4 +
Updated by cduryee over 8 years ago
merged to 2.5-dev and master
+ This comment was cloned from Bugzilla #1139703 comment 5 +
Updated by cduryee over 8 years ago
fixed in pulp 2.6.0-0.2.beta
+ This comment was cloned from Bugzilla #1139703 comment 6 +
Updated by pthomas@redhat.com over 8 years ago
verified
[root@cloud-qe-4 CDN]# rpm -qa pulp-server
pulp-server-2.6.0-0.5.beta.el7.noarch
[root@cloud-qe-4 CDN]#
[root@cloud-qe-4 ~]# pulp-admin rpm repo sync schedules list --repo-id pulp-el6+----------------------------------------------------------------------+
Schedules
--------------------------------------------------------------------
Schedule: 2015-02-02T01:38:00Z/PT1H
Id: 54ca7bbb9f9b81721ab565a3
Enabled: True
Next Run: 2015-02-02T13:38:00Z
[root@cloud-qe-4 CDN]# pulp-admin rpm repo sync schedules list --repo-id pulp-el6
--------------------------------------------------------------------
Schedules
--------------------------------------------------------------------
Schedule: 2015-02-02T01:38:00Z/PT1H
Id: 54ca7bbb9f9b81721ab565a3
Enabled: True
Next Run: 2015-02-02T15:38:00Z
[root@cloud-qe-4 CDN]# pulp-admin rpm repo sync schedules update --repo-id pulp-el6 --schedule-id 54ca7bbb9f9b81721ab565a3 -s 2015-02-02T01:38:00Z/PT24H
Successfully updated schedule
[root@cloud-qe-4 CDN]# pulp-admin rpm repo sync schedules list --repo-id pulp-el6
--------------------------------------------------------------------
Schedules
--------------------------------------------------------------------
Schedule: 2015-02-02T01:38:00Z/PT24H
Id: 54ca7bbb9f9b81721ab565a3
Enabled: True
Next Run: 2015-02-03T00:38:00Z
+ This comment was cloned from Bugzilla #1139703 comment 7 +
Updated by rbarlow over 8 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE
.