Project

Profile

Help

Issue #4423

closed

Sync schedules show next runs being current time

Added by both0 about 5 years ago. Updated about 5 years ago.

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

Description

I created 4 repos and created 4 identical schedules for them, using these commands:

pulp-admin rpm repo sync schedules create -s '2019-02-11T02:00Z/P1D' --repo-id=centos7_base
pulp-admin rpm repo sync schedules create -s '2019-02-11T02:00Z/P1D' --repo-id=centos7_epel
pulp-admin rpm repo sync schedules create -s '2019-02-11T02:00Z/P1D' --repo-id=centos7_extras
pulp-admin rpm repo sync schedules create -s '2019-02-11T02:00Z/P1D' --repo-id=centos7_updates

When viewing the schedule for one repo with a couple seconds interval:

[0m+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

Schedule: 2019-02-11T02:00Z/P1D
Id:       5c659b70aa12c71447445a04
Enabled:  True
Next Run: 2019-02-14T16:49:24Z

[0m+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

Schedule: 2019-02-11T02:00Z/P1D
Id:       5c659b70aa12c71447445a04
Enabled:  True
Next Run: 2019-02-14T16:49:28Z

and with date

[t@pulp ~]$ date
Thu Feb 14 17:12:28 UTC 2019
[t@pulp ~]$ pulp-admin rpm repo sync schedules list --repo-id=centos7_base
+----------------------------------------------------------------------+
                               Schedules
+----------------------------------------------------------------------+

Schedule: 2019-02-11T02:00Z/P1D
Id:       5c659b70aa12c71447445a04
Enabled:  True
Next Run: 2019-02-14T17:12:31Z

Also available in: Atom PDF