Unintentionally, this conversation went off-list on Friday. I'm sending this note to let everyone know that the thread is closed.
JFYI, the summary of the discussion: - .treeinfo error is not an error, it's just a way of Pulp to find distribution(kickstart) tree. Maybe this message should be logged at debug level not to confuse people. - Joey's issue was mostly environmental - EPEL7URL http://download.fedoraproject.org/pub/epel/7/x86_64/ doesn't work for sync, but https://dl.fedoraproject.org/pub/epel/7/x86_64/ does. Needs investigation. Tanya On Fri, Nov 8, 2019 at 8:18 PM Dumont, Joey <[email protected]> wrote: > Hi, > > > Versions: > > > "versions": [ > { > "component": "pulpcore", > "version": "3.0.0rc7" > }, > { > "component": "pulpcore-plugin", > "version": "0.1.0rc7" > }, > { > "component": "pulp_rpm", > "version": "3.0.0b7" > }, > { > "component": "pulp_file", > "version": "0.1.0b4" > } > ] > } > > Relevant error messages I found in journalctl: > > pulp: backoff:ERROR: Giving up _run(...) after 1 tries > (aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found', > url=URL('https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/treeinfo' > )) > Giving up _run(...) after 1 tries > (aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found', > url=URL('https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/treeinfo' > )) > pulp: backoff:ERROR: Giving up _run(...) after 1 tries > (aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found', > url=URL(' > https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/.treeinfo')) > Giving up _run(...) after 1 tries > (aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found', > url=URL(' > https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/7/x86_64/.treeinfo')) > pulp: pulp_rpm.app.tasks.synchronizing:INFO: Synchronizing: > repository=test-rpm remote=test-rpm-remote > pulp: rq.worker:INFO: Cleaning registries for queue: resource-manager > pulp: rq.worker:INFO: resource-manager: Job OK > (6cc2e593-83b5-4ef9-9bcf-84175707670c) > pulp: rq.worker:INFO: > [email protected]: > e8c293fe-e5f2-402f-a3e3-a33f421ed8cb > 127.0.0.1 - admin [06/Nov/2019:14:15:38 +0000] "POST > /pulp/api/v3/remotes/rpm/rpm/fa1c9782-11cb-415f-b710-17df275a82de/sync/ > HTTP/1.1" 202 67 "-" "HTTPie/0.9.4" > pulp: rq.worker:INFO: resource-manager: > 6cc2e593-83b5-4ef9-9bcf-84175707670c > > It's looking for a .treeinfo file, without success, then failing. What is > a .treeinfo file? > > > Joey Dumont > > Technical Advisor, Knowledge, Information, and Technology Services > National Research Council Canada / Governement of Canada > [email protected] / Tel: 613-990-8152 / Cell: 438-340-7436 > > Conseiller technique, Services du savoir, de l'information et de la > technologie > Conseil national de recherches Canada / Gouvernement du Canada > [email protected] / Tél.: 613-990-8152 / Tél. cell.: 438-340-7436 > ------------------------------ > *From:* Tatiana Tereshchenko <[email protected]> > *Sent:* 08 November 2019 14:02 > *To:* Dumont, Joey > *Cc:* [email protected] > *Subject:* Re: [Pulp-list] How to troubleshoot: Cannot sync EPEL > > Hi Joey, > > Can you please share which version you are running? > http GET :24817/pulp/api/v3/status/ > > Logs should be available in the standard location depending on your system > and configuration. > E.g. if you have journalctl, you can see pulp logs there. > > Tanya > > > On Wed, Nov 6, 2019 at 3:18 PM Dumont, Joey <[email protected]> > wrote: > >> I am trying to sync the EPEL repo using the pulp-rpm plugin. Here's the >> repo info: >> >> >> http GET >> :24817/pulp/api/v3/remotes/rpm/rpm/fa1c9782-11cb-415f-b710-17df275a82de/ >> { >> "download_concurrency": 20, >> "name": "test-rpm-remote", >> "policy": "immediate", >> "proxy_url": null, >> "pulp_created": "2019-10-31T15:51:43.651250Z", >> "pulp_href": >> "/pulp/api/v3/remotes/rpm/rpm/fa1c9782-11cb-415f-b710-17df275a82de/", >> "pulp_last_updated": "2019-11-05T19:56:38.242131Z", >> "ssl_ca_certificate": null, >> "ssl_client_certificate": null, >> "ssl_client_key": null, >> "ssl_validation": true, >> "url": "http://download.fedoraproject.org/pub/epel/7/x86_64/"; >> } >> >> >> Here's the repo used to do the sync: >> >> http GET >> :24817/pulp/api/v3/repositories/086a95b2-6aaa-4786-b317-f0e91fa2b800/ >> { >> "description": null, >> "latest_version_href": null, >> "name": "test-rpm", >> "plugin_managed": false, >> "pulp_created": "2019-10-31T15:41:08.128783Z", >> "pulp_href": >> "/pulp/api/v3/repositories/086a95b2-6aaa-4786-b317-f0e91fa2b800/", >> "versions_href": >> "/pulp/api/v3/repositories/086a95b2-6aaa-4786-b317-f0e91fa2b800/versions/" >> } >> >> >> When trying to sync using >> >> http POST >> :24817/pulp/api/v3/remotes/rpm/rpm/fa1c9782-11cb-415f-b710-17df275a82de/sync/ >> repository=/pulp/api/v3/repositories/086a95b2-6aaa-4786-b317-f0e91fa2b800/ >> >> >> The task reports a failed state after a couple seconds, with no traceback >> or description. I can see that 4404 errata were parsed, and some metadata >> files, but no error messages. Where can I see a more detailed log of what >> happened in that task to troubleshoot this? >> >> $ http :24817/pulp/api/v3/tasks/ | jq '.results[0]' >> { >> "pulp_href": "/pulp/api/v3/tasks/e8c293fe-e5f2-402f-a3e3-a33f421ed8cb/", >> "pulp_created": "2019-11-06T14:15:38.444316Z", >> "state": "failed", >> "name": "pulp_rpm.app.tasks.synchronizing.synchronize", >> "started_at": "2019-11-06T14:15:38.561114Z", >> "finished_at": "2019-11-06T14:16:08.555068Z", >> "error": { >> "traceback": "", >> "description": "None" >> }, >> "worker": "/pulp/api/v3/workers/fa48d3b3-3341-4d6d-a3a4-31386d2f7580/", >> "parent": null, >> "spawned_tasks": [], >> "progress_reports": [ >> { >> "message": "Downloading Metadata Files", >> "code": "downloading.metadata", >> "state": "running", >> "total": null, >> "done": 5, >> "suffix": null >> }, >> { >> "message": "Downloading Artifacts", >> "code": "downloading.artifacts", >> "state": "running", >> "total": null, >> "done": 0, >> "suffix": null >> }, >> { >> "message": "Parsed Packages", >> "code": "parsing.packages", >> "state": "waiting", >> "total": null, >> "done": 0, >> "suffix": null >> }, >> { >> "message": "Associating Content", >> "code": "associating.content", >> "state": "running", >> "total": null, >> "done": 0, >> "suffix": null >> }, >> { >> "message": "Parsed Erratum", >> "code": "parsing.errata", >> "state": "running", >> "total": 4404, >> "done": 4404, >> "suffix": null >> } >> ], >> "created_resources": [ >> null >> ], >> "reserved_resources_record": [ >> "/pulp/api/v3/remotes/rpm/rpm/fa1c9782-11cb-415f-b710-17df275a82de/", >> "/pulp/api/v3/repositories/086a95b2-6aaa-4786-b317-f0e91fa2b800/" >> ] >> } >> >> >> >> >> >> Thanks, >> >> >> >> Joey Dumont >> >> Technical Advisor, Knowledge, Information, and Technology Services >> National Research Council Canada / Governement of Canada >> [email protected] / Tel: 613-990-8152 / Cell: 438-340-7436 >> >> Conseiller technique, Services du savoir, de l'information et de la >> technologie >> Conseil national de recherches Canada / Gouvernement du Canada >> [email protected] / Tél.: 613-990-8152 / Tél. cell.: >> 438-340-7436 >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list > >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
