| Summary: | Misleading error log in certain repo sync cases | ||
|---|---|---|---|
| Product: | [Retired] Pulp | Reporter: | Jay Dobies <jason.dobies> |
| Component: | user-experience | Assignee: | Jay Dobies <jason.dobies> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Preethi Thomas <pthomas> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | skarmark |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-09 17:09:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
I spoke with jconnor. We're punting on this for now and will address with the coordinator layer being added in the future. Fixed in v2. Ping jconnor for help in a test case to show it isn't an issue. verified
You see the following in pulp.log
2012-11-06 13:56:52,128 5328:140239580530432: pulp.server.dispatch.scheduler:INFO: scheduler:114 Scheduled CallRequest: RepoSyncManager.sync(u'scientific', sync_config_override={}, importer_config={}, importer_instance=<yum_importer.importer.YumImporter object at 0x7f8bc8ec01d0>): postponed [reasons: [{'operation': u'update',
u'resource_id': u'scientific',
u'resource_type': u'repository'}]]
Pulp v2.0 released |
I have a repo scheduled to sync. I triggered a manual (immediate) sync. During that immediate sync run, the scheduled sync time was passed and the scheduled task attempted to start. It couldn't since the immediate sync was running (that's correct). But I saw this in the logs: 2011-06-21 13:51:34,575 26444:140532420417280: pulp.server.api.repo_sync:ERROR: repo_sync:207 We saw sync was in progress for [rhel-server-6-releases-6Server-x86_64] 2011-06-21 13:51:35,201 26444:140532420417280: pulp.server.tasking.task:ERROR: task:380 Task failed: Task f70023e3-9c2e-11e0-bd00-00508d977dff: _sync(rhel-server-6-releases-6Server-x86_64, synchronizer=<pulp.server.api.synchronizers.YumSynchronizer object at 0x7fd070aa0e90>, progress_callback=<bound method RepoSyncTask.progress_callback of <pulp.server.api.repo_sync_task.RepoSyncTask object at 0x7fd070aa0e50>>) Traceback (most recent call last): File "/home/jdob/code/pulp/src/pulp/server/tasking/task.py", line 329, in run result = self.callable(*self.args, **self.kwargs) File "/home/jdob/code/pulp/src/pulp/server/api/repo_sync.py", line 208, in _sync raise ConflictingOperationException(_('Sync for repo [%s] already in progress') % repo_id) ConflictingOperationException: Sync for repo [rhel-server-6-releases-6Server-x86_64] already in progress I totally get why it occurred, but the fact remains that users will see this and not have that understanding. It looks like an error, but it's a case we planned for and gracefully handle. We need to clean up this output.