Actions
Story #1699
closedAs a user, if I cancel the repo sync, I don't want the auto-publish to happen.
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Currently some of the plugins trigger the auto-publish task even if the sync task was cancelled. I think if sync get's cancelled, publish should not happen.
Example of behaviour that should be fixed:
Beginning sync for repository <pup>
Feb 19 15:07:55 ina pulp: pulp_puppet.plugins.importers.forge:INFO: Beginning metadata retrieval for repository <pup>
Feb 19 15:07:55 ina pulp: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (1): forge.puppetlabs.com
Feb 19 15:08:17 ina pulp: pulp_puppet.plugins.importers.forge:INFO: Retrieving modules for repository <pup>
Feb 19 15:08:17 ina pulp: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (1): forge.puppetlabs.com
Feb 19 15:08:37 ina pulp: celery.worker.control:INFO: Terminating e56c4e24-0ec7-4026-b09a-e823eee932ad (15)
Feb 19 15:08:37 ina pulp: pulp.server.async.tasks:INFO: Task canceled: e56c4e24-0ec7-4026-b09a-e823eee932ad.
Feb 19 15:08:38 ina pulp: celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._queue_reserved_task[3d4d01b6-f53f-4025-a555-15673b026e73]
Feb 19 15:08:38 ina pulp: celery.worker.job:INFO: Task pulp.server.managers.repo.sync.sync[e56c4e24-0ec7-4026-b09a-e823eee932ad] succeeded in 44.3218306329s: <pulp.server.async.tasks.TaskResult object at 0x7f7688e1b350>
Feb 19 15:08:38 ina pulp: celery.worker.job:INFO: Task pulp.server.async.tasks._release_resource[7176d19c-9b55-4122-ac93-df6900b71a83] succeeded in 0.0304714299273s: None
Feb 19 15:08:38 ina pulp: celery.worker.strategy:INFO: Received task: pulp.server.managers.repo.publish.publish[13a3b6b1-bd0d-4596-8794-1bd75ad031ee]
Feb 19 15:08:38 ina pulp: celery.worker.job:INFO: Task pulp.server.async.tasks._queue_reserved_task[3d4d01b6-f53f-4025-a555-15673b026e73] succeeded in 0.0727513269521s: None
Feb 19 15:08:38 ina pulp: celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._release_resource[33f49d92-7af3-4af7-adc3-69150dfb928a]
Feb 19 15:08:38 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Beginning publish for repository <pup>
Feb 19 15:08:38 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Initializing build directory for repository <pup>
Feb 19 15:08:39 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Creating symlinks for modules in repository <pup>
Feb 19 15:08:39 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Generating metadata for repository <pup>
Feb 19 15:08:39 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Making newly built repository live for repository <pup>
Feb 19 15:08:39 ina pulp: pulp_puppet.plugins.distributors.publish:INFO: Cleaning up build directory for repository <pup>
Feb 19 15:08:39 ina pulp: celery.worker.job:INFO: Task pulp.server.managers.repo.publish.publish[13a3b6b1-bd0d-4596-8794-1bd75ad031ee] succeeded in 0.419491785113s: {'exception': None, 'repo_id': u'pup', 'traceback': None, 'started': '2016-02-19T14:08:38Z', '_ns': u'repo_publish_results',...
Feb 19 15:08:39 ina pulp: celery.worker.job:INFO: Task pulp.server.async.tasks._release_resource[33f49d92-7af3-4af7-adc3-69150dfb928a] succeeded in 0.0182418890763s: None
Related issues
Updated by ipanova@redhat.com about 8 years ago
- Sprint Candidate changed from No to Yes
Updated by ipanova@redhat.com about 8 years ago
- Related to Story #1700: Cancellation handler for sync should exit immediately and never call into the plugin's code added
Updated by bmbouter almost 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter almost 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
Actions