Bug 674592 - repo sync doesn't seem to be getting invoked on repos that has schedules defined.
Summary: repo sync doesn't seem to be getting invoked on repos that has schedules defi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: z_other
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pradeep Kilambi
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-02 15:24 UTC by Preethi Thomas
Modified: 2012-02-24 20:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-24 20:15:43 UTC


Attachments (Terms of Use)

Description Preethi Thomas 2011-02-02 15:24:48 UTC
Description of problem:


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


On repositories that has --schedules defined, the sync doesn't seem to be getting invoked.
I don't see any information in log.

1. create a repo with --schedules defined.
2. Wait for the sync to get invoked.

Comment 1 Todd Sanders 2011-02-09 16:44:51 UTC
Tracking along with RFE to revamp scheduler.

Comment 2 Sayli Karmarkar 2011-07-15 06:24:03 UTC
This should be fixed.

Comment 3 Preethi Thomas 2011-08-31 17:25:08 UTC
verified
[root@preethi ~]# rpm -q pulp
pulp-0.0.228-1.fc15.noarch

[root@preethi ~]# pulp-admin repo update --id=f14  --interval PT1H
Successfully updated repository [ f14 ]

2011-08-31 13:33:47,712 21115:140533267687168: pulp.server.api.repo_sync:INFO: repo_sync:223 Sync invoked for repo <f14>
2011-08-31 13:33:47,721 21115:140533267687168: pulp.server.api.repo_sync:INFO: repo_sync:237 Sync of f14 starting, skip_dict = {}
2011-08-31 13:33:47,738 21115:140533267687168: pulp.server.api.synchronizers:INFO: synchronizers:525 cacert = <None>, cert = <None>

Comment 4 Preethi Thomas 2012-02-24 20:15:43 UTC
Pulp v1.0 is released
Closed Current Release.

Comment 5 Preethi Thomas 2012-02-24 20:17:19 UTC
Pulp v1.0 is released.


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