Project

Profile

Help

Issue #516

closed

Updating a sync plan's frequency does not seem to affect future syncs

Added by jsherril@redhat.com about 9 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.4.1
Platform Release:
2.6.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

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 +

Also available in: Atom PDF