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"
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.
Moving back to NEW status for now.
picking BZ back up
https://github.com/pulp/pulp/pull/1170
merged to 2.5-dev and master
fixed in pulp 2.6.0-0.2.beta
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
Moved to https://pulp.plan.io/issues/516
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
*** Bug 1158933 has been marked as a duplicate of this bug. ***
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
upstream lists this bug as resolved in pulp 2.6.0 which is being shipped in Satellite 6.1. I am moving this to on_qa.
Verified in Satellite 6.1 Snap 3
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.