Description of problem: If you have multiple sync schedules for a repo, pulp.log has a resource not found error. Version-Release number of selected component (if applicable): [root@pulp-candidate ~]# rpm -qa pulp-rpm-server pulp-rpm-server-2.0.1-1.fc17.noarch [root@pulp-candidate ~]# How reproducible: Steps to Reproduce: 1. Add multiple sync schedules for a repo. 2. 3. Actual results: 2012-08-30 13:08:29,725 26465:140337209124608: pulp.server.dispatch.task:INFO: task:163 Task 5201cdde-f2c5-11e1-a52f-5452003c7b52: CallRequest: RepoSyncManager.sync(u'zoo', sync_config_override={}) FAILED 2012-08-30 13:08:59,709 26465:140339732526848: pulp.server.dispatch.scheduler:INFO: scheduler:101 Scheduled CallRequest: RepoSyncManager.sync(u'zoo', sync_config_override={}): accepted [reasons: []] 2012-08-30 13:08:59,867 26465:140337209124608: pulp.server.dispatch.task:ERROR: task:133 Missing resource(s): resource_id=zoo Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pulp/server/dispatch/task.py", line 130, in _run result = call(*args, **kwargs) File "/usr/lib/python2.7/site-packages/pulp/server/managers/repo/sync.py", line 124, in sync raise MissingResource(repo_id) MissingResource: Missing resource(s): resource_id=zoo 2012-08-30 13:08:59,964 26465:140337209124608: pulp.server.dispatch.task:INFO: task:163 Task 63ec0ea6-f2c5-11e1-9a97-5452003c7b52: CallRequest: RepoSyncManager.sync(u'zoo', sync_config_override={}) FAILED Expected results: Additional info:
Preethi - can you consistently reproduce it?
No, this seems like a non-issue. Closing