Problem:
Python Repository, when synced with Python PyPI remote, always stays in version 0, i.e. no packages are added.
Our Pulp node is behind a HTTP proxy.
This issue was reported before:
And resolved as part of “python”: “3.12.1”. But it has come back again.
Expected outcome:
The repository version increases after syncs, and packages get added to the repository.
Pulpcore version:
3.75.0
Pulp plugins installed and their versions:
“versions”: {
“deb”: “3.5.1”,
“npm”: “0.3.2”,
“rpm”: “3.29.0”,
“core”: “3.75.0”,
“file”: “3.75.0”,
“maven”: “0.10.0”,
“ostree”: “2.4.6”,
"python": “3.13.2”,
“ansible”: “0.24.3”,
“certguard”: “3.75.0”,
“container”: “2.24.1”
}
Operating system - distribution and version:
NAME=“Alma Linux”
VERSION=“8.9”
Other relevant data:
$ pulp python remote list
[
{
“pulp_href”: “/pulp/api/v3/remotes/python/python/019601ed-f52b-7d93-a34e-d3d7ae7e2b79/”,
“prn”: “prn:python.pythonremote:019601ed-f52b-7d93-a34e-d3d7ae7e2b79”,
“pulp_created”: “2025-04-04T17:51:34.188686Z”,
“pulp_last_updated”: “2025-04-04T17:51:34.188704Z”,
“name”: “TEST-PyPI”,
“url”: “https://pypi-dot-org/”,
“ca_cert”: null,
“client_cert”: null,
"tls_validation": false,
"proxy_url": “http://X.X.X.X:8080/”,
“pulp_labels”: {
“OS”: “PyPI”
},
“download_concurrency”: 10,
“max_retries”: null,
"policy": “immediate”,
“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”: [
“absl-py==2.1.0”,
“addict==2.4.0”,
“aiofiles==22.1.0”,
“aiohttp-retry==2.8.3”,
“aiohttp==3.9.5”,
“aiosignal==1.3.1”
],
“excludes”: [],
“prereleases”: true,
“package_types”: [
“sdist”,
“bdist_wheel”
],
“keep_latest_packages”: 0,
“exclude_platforms”: [
“freebsd”,
“macos”
]
}
]
Sync task shows no artifact has been downloaded, but no errors either:
{
“pulp_href”: “/pulp/api/v3/tasks/019601ee-0a4e-7990-b421-8c106a439593/”,
“prn”: “prn:core.task:019601ee-0a4e-7990-b421-8c106a439593”,
“pulp_created”: “2025-04-04T17:51:39.599607Z”,
“pulp_last_updated”: “2025-04-04T17:51:39.599635Z”,
"state": “completed”,
“name”: “pulp_python.app.tasks.sync.sync”,
“logging_cid”: “9460bf807d594bc28b609f3185f3509d”,
“created_by”: “/pulp/api/v3/users/1/”,
“unblocked_at”: “2025-04-04T17:51:39.621305Z”,
“started_at”: “2025-04-04T17:51:39.712351Z”,
“finished_at”: “2025-04-04T17:57:55.062394Z”,
“error”: null,
“worker”: “/pulp/api/v3/workers/019601ec-751c-75b0-b70e-45d2e0d65a9c/”,
“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”: [
“prn:python.pythonrepository:019601ed-e754-7fb3-bf0e-e78edfc76583”,
“shared:prn:python.pythonremote:019601ed-f52b-7d93-a34e-d3d7ae7e2b79”,
“shared:prn:core.domain:62823342-753d-4170-b485-8259710b2f00”
]
}
This issue was reported before:
And resolved as part of “python”: “3.12.1”. But it has come back again.
Not everyone can do that, of course - but it gives us a lot more confidence that the PR is fixing the right thing, when we don’t have a local reproducer.