Python sync is failing

Support
#1

Problem:
The python repo doesn’t sync, it start and complete but nothing is retrieved.

Expected outcome:

**Pulpcore version: 3.22.2

Pulp plugins installed and their versions:
“component”: “rpm”, “version”: “3.19.0”,
“component”: “python”, “version”: “3.8.0”,
“component”: “deb”, “version”: “2.20.1”,
“component”: “container”, “version”: “2.14.3”,
“component”: “file”, “version”: “1.12.0”,
“component”: “certguard”, “version”: “1.5.7”,
“component”: “ansible”, “version”: “0.16.0”,
“component”: “maven”, “version”: “0.3.3”,

Operating system - distribution and version:
NAME=“Red Hat Enterprise Linux”
VERSION=“8.7 (Ootpa)”

Other relevant data:
pulp python repository sync --name foo --remote bar
Started background task /pulp/api/v3/tasks/8eaa1f18-3e6f-4c2a-b1b0-28218b3099a3/
…Done.

{
“pulp_href”: “/pulp/api/v3/tasks/8eaa1f18-3e6f-4c2a-b1b0-28218b3099a3/”,
“pulp_created”: “2023-02-24T12:04:00.969248Z”,
“state”: “completed”,
“name”: “pulp_python.app.tasks.sync.sync”,
“logging_cid”: “1666cc5cd0b7499083d3574891fd3ed3”,
“started_at”: “2023-02-24T12:04:01.026279Z”,
“finished_at”: “2023-02-24T12:04:39.661178Z”,
“error”: null,
“worker”: “/pulp/api/v3/workers/c8b64b18-984c-4f81-be66-3ec40a908883/”,
“parent_task”: null,
“child_tasks”: [],
“task_group”: null,
“progress_reports”: [
{
“message”: “Fetching Project Metadata”,
“code”: “sync.fetching.project”,
“state”: “completed”,
“total”: null,
“done”: 0,
“suffix”: null
},
{
“message”: “Downloading Artifacts”,
“code”: “sync.downloading.artifacts”,
“state”: “completed”,
“total”: null,
“done”: 0,
“suffix”: null
},
{
“message”: “Associating Content”,
“code”: “associating.content”,
“state”: “completed”,
“total”: null,
“done”: 0,
“suffix”: null
}
],
“created_resources”: [],
“reserved_resources_record”: [
“/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/”,
“shared:/pulp/api/v3/remotes/python/python/6a761c2b-f8d9-49c3-bda5-c1e580e08a03/”
]
}

Where can I find more debugging?

#2

Please post the entire set of commands you used to get to the point where nothing is synced. That way others can try to reproduce the problem on their own pulp instances.

In particular, how you created the remote “bar” that you used is crucial. The full output of pulp python remote show --name bar might do the trick.

You could also check if there is any output to the system log (on your pulp instance) while you are running your sync command using journalctl. But the main thing to post is how you created the remote.

1 Like
#3

pulp python remote show --name bar
{
“pulp_href”: “/pulp/api/v3/remotes/python/python/f794a78f-bbf6-4b36-a782-260284ca8801/”,
“pulp_created”: “2023-02-24T12:41:17.081924Z”,
“name”: “bar”,
“url”: “https://pypi.org/”,
“ca_cert”: null,
“client_cert”: null,
“tls_validation”: false,
“proxy_url”: “http://161.89.61.209:8080”,
“pulp_labels”: {},
“pulp_last_updated”: “2023-02-24T12:41:17.081975Z”,
“download_concurrency”: null,
“max_retries”: null,
“policy”: “on_demand”,
“total_timeout”: null,
“connect_timeout”: null,
“sock_connect_timeout”: null,
“sock_read_timeout”: null,
“headers”: null,
“rate_limit”: null,
“hidden_fields”: [
{
“name”: “client_key”,
“is_set”: false
},
{
“name”: “proxy_username”,
“is_set”: false
},
{
“name”: “proxy_password”,
“is_set”: false
},
{
“name”: “username”,
“is_set”: false
},
{
“name”: “password”,
“is_set”: false
}
],
“includes”: [
“shelf-reader”
],
“excludes”: [],
“prereleases”: true,
“package_types”: [],
“keep_latest_packages”: 0,
“exclude_platforms”: []
}

pulp python repository show --name foo
{
“pulp_href”: “/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/”,
“pulp_created”: “2023-02-24T08:41:00.948563Z”,
“versions_href”: “/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/versions/”,
“pulp_labels”: {},
“latest_version_href”: “/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/versions/0/”,
“name”: “foo”,
“description”: null,
“retain_repo_versions”: null,
“remote”: null,
“autopublish”: false
}

pulp python repository version show --repository foo
{
“pulp_href”: “/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/versions/0/”,
“pulp_created”: “2023-02-24T08:41:00.955887Z”,
“number”: 0,
“repository”: “/pulp/api/v3/repositories/python/python/9b34b8c7-87cf-48d1-8533-b510220c9dfc/”,
“base_version”: null,
“content_summary”: {
“added”: {},
“removed”: {},
“present”: {}
}
}

Within in the pulp container I can update/install pi module.

#4

Syncing with proxies is currently broken in pulp_python. Once this is merged: https://github.com/pulp/pulp_python/pull/588, I will backport it and release 3.8.1 to fix this problem.

3 Likes