Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJustin Sherrill
2014-10-30 14:25:19 UTC
+++ This bug was initially created as a clone of Bug #1139703 +++
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"
--- Additional comment from Michael Hrivnak on 2014-09-09 10:56:20 EDT ---
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.
--- Additional comment from Chris Duryee on 2014-09-17 12:41:01 EDT ---
Moving back to NEW status for now.
--- Additional comment from Chris Duryee on 2014-09-22 08:40:45 EDT ---
picking BZ back up
--- Additional comment from Chris Duryee on 2014-09-22 18:23:23 EDT ---
https://github.com/pulp/pulp/pull/1170
--- Additional comment from Chris Duryee on 2014-09-29 20:04:41 EDT ---
merged to 2.5-dev and master