Project

Profile

Help

Issue #922

Updated by bmbouter almost 9 years ago

It I noticed today that it seems I cannot update an existing sync, publish, or consumer action sync schedule. For example, I had an existing schedule, and I wanted to change it to run next in about four minutes (so that it's more than 90 seconds out, giving the scheduler enough time to notice the change). Here is me listing the schedule, and updating it to a new value: 

 <pre> 
 [vagrant@cloud-basebox pulp]$ pulp-admin rpm repo sync schedules list --repo-id zoo 
 +----------------------------------------------------------------------+ 
                                Schedules 
 +----------------------------------------------------------------------+ 

 Schedule: 2015-04-27T21:24:00Z/P1D 
 Id:         553be0de7517d40591882021 
 Enabled:    True 
 Next Run: 2015-04-28T18:48:00Z 


 [vagrant@cloud-basebox pulp]$ pulp-admin rpm repo sync schedules update --repo-id zoo --schedule-id 553be0de7517d40591882021 --schedule 2015-04-27T21:32:00Z/P1D 
 Successfully updated schedule 

 [vagrant@cloud-basebox pulp]$ date -u 
 Mon Apr 27 21:28:44 UTC 2015 
 </pre> 

 The Next Run continues to show 2015-04-28T18:48:00Z well past the new schedule start time, and according to the logs the new schedule never fired (I didn't see a sync happen in the log.) 

 A workaround is to delete the existing schedule and create a new schedule with the desired start time.

Back