[Pulp-list] sync task status misreports sync as still in progress

[Urwin, Paul]

Hello,

I am seeing pulp-admin report that a sync is still in progress when it appears that in reality it has in fact completed.  The status output gets stuck on the final package being downloaded, this is not a one-off occurrence.

For example, I synchronised this repo earlier, and the pulp-admin status output shows that the downloads paused at the penultimate package download:


[root at shou18l585g5_13 ~]# pulp-admin rpm repo sync status --repo-id=rhel7-htb
+----------------------------------------------------------------------+
                     Repository Status [rhel7-htb]
+----------------------------------------------------------------------+

This command may be exited by pressing ctrl+c without affecting the actual
operation on the server.

Publishing packages...
[==================================================] 100%
Packages: 10991/10991 items
... completed

Publishing distributions...
[==================================================] 100%
Distributions: 0/0 items
... completed

Generating metadata
[-]
... completed

Publishing repository over HTTPS
[-]
... completed

Publishing repository over HTTP
[-]
... completed

Downloading metadata...
[-]
... completed

Downloading repository content...
[================================================  ] 97%
RPMs:       467/468 items
Delta RPMs: 0/0 items


However I can see in the pulp.log that in fact it seems to have completed, the metadata generated and the repository published....

2014-01-31 05:21:48,092 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: Performing per unit metadata merge on 491 units
2014-01-31 05:21:56,799 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: per unit metadata merge completed in 8.69609498978 seconds
2014-01-31 05:21:58,110 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: generate_yum_metadata finished processing 10991 units
2014-01-31 05:25:30,270 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: Modifying repo for comps metadata
2014-01-31 05:25:30,749 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: modifyrepo with /var/lib/pulp/working/repos/rhel7-htb/distributors/yum_distributor/group.xml on /var/lib/pulp/working/repos/rhel7-htb/distributors/yum_distributor/repodata finished
2014-01-31 05:25:30,764 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: updateinfo xml path does not exist; skipping merge
2014-01-31 05:25:30,770 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: check scratchpad for any repodata
2014-01-31 05:25:30,789 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: Modifying repo for productid metadata
2014-01-31 05:25:31,098 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: modifyrepo with /var/lib/pulp/working/repos/rhel7-htb/distributors/yum_distributor/productid.xml on /var/lib/pulp/working/repos/rhel7-htb/distributors/yum_distributor/repodata finished
2014-01-31 05:25:31,123 pulp.plugins.pulp_rpm.yum_plugin.metadata:INFO: Metadata generation finished in 288.064763069 seconds
2014-01-31 05:25:32,745 pulp.plugins.yum_distributor.distributor:INFO: HTTPS Publishing repo <rhel7-htb> to </var/lib/pulp/published/https/repos/rhel7-htb>
2014-01-31 05:25:32,889 pulp.plugins.yum_distributor.distributor:INFO: HTTP Publishing repo <rhel7-htb> to </var/lib/pulp/published/http/repos/rhel7-htb>
2014-01-31 05:25:33,091 pulp.plugins.yum_distributor.distributor:INFO: Publish complete:  summary = <{'num_package_units_errors': 0, 'https_publish_dir': u'/var/lib/pulp/published/https/repos/rhel7-htb', 'num_package_categories_published': 9, 'http_publish_dir': u'/var/lib/pulp/published/http/repos/rhel7-htb', 'skip_metadata_update': False, 'num_distribution_units_published': 0, 'num_package_groups_published': 69, 'num_package_units_attempted': 10991, 'num_package_units_published': 10991, 'num_distribution_units_attempted': 0, 'num_distribution_units_errors': 0, 'relative_path': u'rhel7-htb'}>, details = <{'errors': [], 'time_metadata_sec': 288.10581994056702}>

The original sync was called with:

# pulp-admin rpm repo sync run --repo-id=rhel7-htb


Here is the task response body:

{"task_group_id": "5af5d56c-4907-4ea8-b3d9-c2ebd0e64644", "exception": null, "traceback": null, "_href": "/pulp/api/v2/tasks/ef540a92-4fc7-4b1f-9db8-ee22416f1bac/", "task_id": "ef540a92-4fc7-4b1f-9db8-ee22416f1bac", "call_request_tags": ["pulp:repository:rhel7-htb", "pulp:action:sync"], "reasons": [], "start_time": "2014-01-31T11:20:04Z", "tags": ["pulp:repository:rhel7-htb", "pulp:action:sync"], "state": "running", "finish_time": null, "dependency_failures": {}, "schedule_id": null, "progress": {"yum_importer": {"content": {"size_total": 521257756, "items_left": 1, "items_total": 468, "state": "IN_PROGRESS", "size_left": 13564188, "details": {"rpm_total": 468, "rpm_done": 467, "drpm_total": 0, "drpm_done": 0}, "error_details": []}, "comps": {"state": "NOT_STARTED"}, "distribution": {"items_total": 0, "state": "NOT_STARTED", "error_details": [], "items_left": 0}, "errata": {"state": "NOT_STARTED"}, "metadata": {"state": "FINISHED"}}}, "call_request_group_id": "5af5d56c-4907-4ea8-b3d9-c2ebd0e64644", "call_request_id": "ef540a92-4fc7-4b1f-9db8-ee22416f1bac", "principal_login": "admin", "response": "accepted", "result": null}


Is this a known bug?

Thanks,

Paul

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.