Project

Profile

Help

Issue #2838

Updating/Adding a sync schedule does not trigger an immediate sync

Added by mikea about 3 years ago. Updated over 1 year ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
1. Low
Version - Python:
Platform Release:
Target Release - Python:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:

Description

In the RPM/Yum plugin whenever you add a sync schedule without a start time in the future (for example, P1D) it starts a sync task immediately.

The Python plugin does not do this. It should be consistent.

History

#1 Updated by ttereshc about 3 years ago

  • Priority changed from Normal to Low
  • Triaged changed from No to Yes
  • Tags deleted (Sync Performance)

#2 Updated by mhrivnak about 3 years ago

Did you schedule this through pulp-admin, or through the API directly?

The logic that chooses when to next run a scheduled task has no idea what kind of task is in question, let alone what type of repo is being acted on. Whatever caused this behavior is hopefully a simple bug along the way. The only possible difference that comes to mind is the chance that pulp-admin's python repo support is passing arguments to the API differently.

#3 Updated by bmbouter about 3 years ago

mikea, You can see exactly the calls that pulp-admin is producing using the -vv flag. It needs to be the first option like pulp-admin -vv rpm repo ...

#4 Updated by mikea about 3 years ago

mhrivnak wrote:

Did you schedule this through pulp-admin, or through the API directly?

The logic that chooses when to next run a scheduled task has no idea what kind of task is in question, let alone what type of repo is being acted on. Whatever caused this behavior is hopefully a simple bug along the way. The only possible difference that comes to mind is the chance that pulp-admin's python repo support is passing arguments to the API differently.

These are schedules created via the API, not pulp-admin. I haven't actually tried doing this with the pulp-admin cli.

My code that creates the schedule is exactly the same regardless of the repo type. The behavior is that when a new schedule is created for yum repositories without a time in the future (P1D, for example), a sync immediately starts. This does not happen with python repositories.

#5 Updated by bmbouter over 1 year ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#6 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF