Bug 1139703

Summary:	Updating a sync plan's frequency does not seem to affect future syncs
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.0	CC:	bbuckingham, bkearney, bmbouter, cduryee, cwelton, daviddavis, dkliban, ggainey, ipanova, jcallaha, lfisher047, mhrivnak, michele, mmccune, pcreech, pthomas, rchan, ttereshc
Target Milestone:	Unspecified	Keywords:	Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1158933 (view as bug list)		Environment:
Last Closed:	2015-08-12 16:02:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1145795, 1158933, 1177908

Description Justin Sherrill 2014-09-09 13:25:13 UTC

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"

Comment 1 Michael Hrivnak 2014-09-09 14:56:20 UTC

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.

Comment 2 Chris Duryee 2014-09-17 16:41:01 UTC

Moving back to NEW status for now.

Comment 3 Chris Duryee 2014-09-22 12:40:45 UTC

picking BZ back up

Comment 4 Chris Duryee 2014-09-22 22:23:23 UTC

https://github.com/pulp/pulp/pull/1170

Comment 5 Chris Duryee 2014-09-30 00:04:41 UTC

merged to 2.5-dev and master

Comment 6 Chris Duryee 2014-12-23 20:52:17 UTC

fixed in pulp 2.6.0-0.2.beta

Comment 7 Preethi Thomas 2015-02-02 15:23:40 UTC

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

Comment 8 Brian Bouterse 2015-02-28 22:18:55 UTC

Moved to https://pulp.plan.io/issues/516

Comment 9 RHEL Program Management 2015-03-03 20:19:43 UTC

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.

Comment 11 Brian Bouterse 2015-03-05 21:55:26 UTC

*** Bug 1158933 has been marked as a duplicate of this bug. ***

Comment 12 pulp-infra@redhat.com 2015-04-23 16:40:24 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 13 Bryan Kearney 2015-04-27 20:28:57 UTC

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.

Comment 15 jcallaha 2015-05-08 12:54:43 UTC

Verified in Satellite 6.1 Snap 3

Comment 16 Bryan Kearney 2015-08-12 16:02:20 UTC

This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.