Bug 959031 - Updating existing sync schedule does not change effective schedule.
Summary: Updating existing sync schedule does not change effective schedule.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: 2.1 Beta
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.3.0
Assignee: Jason Connor
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks: 950743 1017345
TreeView+ depends on / blocked
 
Reported: 2013-05-03 03:17 UTC by Ryan Bowlby
Modified: 2013-12-09 14:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1017345 (view as bug list)
Environment:
Last Closed: 2013-12-09 14:31:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Ryan Bowlby 2013-05-03 03:17:14 UTC
Description of problem:

Updating an existing repositories sync schedule-id to a new interval does not modify the actual interval. Though command shows success and task shows success.


Version-Release number of selected component (if applicable):

2.1.1-0.5.beta.el6.noarch

How reproducible:

Everytime

Steps to Reproduce:
1. Create a sync schedule of P1D for a given repository
2. Verify new sync schedule shows
3. Change existing sync schedule using sync schedules update subcommand to PT8M.

  
Actual results:

Check next scheduled sync interval, it will still be for P1D.

Expected results:

Next scheduled sync interval should reflect the more aggressive interval.

Additional info:

Deletion and Creation of a new schedule is the current workaround.

Comment 1 Michael Hrivnak 2013-06-21 13:25:09 UTC
Is this related to https://bugzilla.redhat.com/show_bug.cgi?id=968524 ?

Comment 2 Jason Connor 2013-09-13 20:42:11 UTC
PR issued for this:
https://github.com/pulp/pulp/pull/612

Comment 3 Jason Connor 2013-09-17 21:35:28 UTC
Fix in commit 51c93ef6371dfb57b12f917e4b2d1103354a5720

Comment 4 Jeff Ortel 2013-09-18 23:58:48 UTC
build: 2.3.0-0.14.alpha

Comment 5 Preethi Thomas 2013-09-20 12:54:34 UTC
verified
[root@pulp-v2-server ~]# rpm -qa pulp-server
pulp-server-2.3.0-0.14.alpha.el6.noarch
[root@pulp-v2-server ~]# 

[root@pulp-v2-server ~]# pulp-admin rpm repo sync schedules list --repo-id zoo1+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

There are no schedules defined for this operation.

[root@pulp-v2-server ~]# pulp-admin rpm repo sync schedules create -s 2013-09-19T12:51:00Z/P1D --repo-id zoo1
Schedule successfully created

[root@pulp-v2-server ~]# 
[root@pulp-v2-server ~]# 
[root@pulp-v2-server ~]# pulp-admin rpm repo sync schedules list --repo-id zoo1+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

Schedule: 2013-09-19T12:51:00Z/P1D
Id:       523c5640d669f05dff00067f
Enabled:  True
Last Run: None
Next Run: 2013-09-21T12:51:00Z


[root@pulp-v2-server ~]# pulp-admin rpm repo sync schedules update -s 2013-09-19T12:51:00Z/PT8M --repo-id zoo1 --schedule-id 523c5640d669f05dff00067f
Successfully updated schedule

[root@pulp-v2-server ~]# pulp-admin rpm repo sync schedules list --repo-id zoo1+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

Schedule: 2013-09-19T12:51:00Z/PT8M
Id:       523c5640d669f05dff00067f
Enabled:  True
Last Run: None
Next Run: 2013-09-20T14:11:00Z


[root@pulp-v2-server ~]#

Comment 6 Preethi Thomas 2013-12-09 14:31:45 UTC
Pulp 2.3 released.


Note You need to log in before you can comment on or make changes to this bug.