Bug 706445 - syncs can be scheduled for past dates.
Summary: syncs can be scheduled for past dates.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-20 15:30 UTC by Preethi Thomas
Modified: 2013-09-09 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-16 16:31:46 UTC


Attachments (Terms of Use)

Description Preethi Thomas 2011-05-20 15:30:13 UTC
Description of problem:

[root@preethi ~]# rpm -q pulp
pulp-0.0.178-1.fc14.noarch

Looks like sync can be scheduled for past.



[root@preethi ~]# pulp-admin repo create --id=-past-sync-schedule --feed=http://repos.fedorapeople.org/repos/pulp/pulp/fedora-14/x86_64/ --interval PT1H --start=2011-05-16T11:15-06:00
Successfully created repository [ -past-sync-schedule ]



From pulp.log

2011-05-20 11:39:52,839 [WARNING][Dummy-2] __init__() @ scheduler.py:124 - IntervalScheduler created with start time more than one interval in the past: 2011-05-16 11:15:00-06:00, 1:00:00
2011-05-20 11:39:52,839 [ERROR][Dummy-2] set_synchronizer() @ repo_sync_task.py:32 - __name__ = pulp.server.api.repo_sync_task
2011-05-20 11:39:52,842 [WARNING][Dummy-2] schedule() @ task.py:270 - Task 67a31680-82f7-11e0-9486-002564a85a58: RepoApi._sync(-past-sync-schedule, synchronizer=<pulp.server.api.repo_sync.YumSynchronizer object at 0x7f17e461d290>) missed 95 scheduled runs
2011-05-20 11:39:52,843 [INFO][Dummy-2] _create_repo() @ util.py:364 - started repo metadata update
2011-05-20 11:39:53,892 [INFO][Dummy-2] _create_repo() @ util.py:370 - [createrepo --database --checksum sha256 --update /var/lib/pulp//repos/repos/pulp/pulp/fedora-14/x86_64 ] on /var/lib/pulp//repos/repos/pulp/pulp/fedora-14/x86_64 finished
2011-05-20 11:39:53,892 [INFO][Dummy-2] create_repo() @ util.py:387 - Noting further to check; we got our fresh metadata

Comment 1 Jason Connor 2011-07-16 16:31:46 UTC
This is expected behavior. A sync scheduled in the past will simply run as soon as possible, possibly logging about missed runs, but we do not consider this an error condition.


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