pulp / pulp/pulp_python

Unexpected synchronization error with a remote repository

Open
#917 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue
Dominant language
Python
Stars
49
Forks
88
Avg merge
1d 10h
Merged PRs (30d)
31

Description

Version

  {
    "component": "core",
    "version": "3.83.2",
    "package": "pulpcore",
    "module": "pulpcore.app",
    "domain_compatible": true
  },
  {
    "component": "python",
    "version": "3.17.0",
    "package": "pulp-python",
    "module": "pulp_python.app",
    "domain_compatible": true
  }

Describe the bug
hello! I want to try to use your project, but I'm facing a problem...
I added:

[
  {
    "pulp_href": "/pulp/api/v3/repositories/python/python/01985ca2-f970-7825-a3f8-122610f262a3/",
    "prn": "prn:python.pythonrepository:01985ca2-f970-7825-a3f8-122610f262a3",
    "pulp_created": "2025-07-30T18:40:41.329775Z",
    "pulp_last_updated": "2025-07-31T08:49:44.630701Z",
    "versions_href": "/pulp/api/v3/repositories/python/python/01985ca2-f970-7825-a3f8-122610f262a3/versions/",
    "pulp_labels": {},
    "latest_version_href": "/pulp/api/v3/repositories/python/python/01985ca2-f970-7825-a3f8-122610f262a3/versions/1/",
    "name": "distro_local",
    "description": null,
    "retain_repo_versions": null,
    "remote": null,
    "autopublish": false
  }
]

remote:

[
  {
    "pulp_href": "/pulp/api/v3/remotes/python/python/01985fcc-9589-7a26-94f7-9c1601fd8fb8/",
    "prn": "prn:python.pythonremote:01985fcc-9589-7a26-94f7-9c1601fd8fb8",
    "pulp_created": "2025-07-31T09:24:59.914051Z",
    "pulp_last_updated": "2025-07-31T09:24:59.914073Z",
    "name": "test-remote",
    "url": "https://mirrors.aliyun.com/pypi",
    "ca_cert": null,
    "client_cert": null,
    "tls_validation": true,
    "proxy_url": null,
    "pulp_labels": {},
    "download_concurrency": null,
    "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": [
      "distro"
    ],
    "excludes": [],
    "prereleases": true,
    "package_types": [],
    "keep_latest_packages": 0,
    "exclude_platforms": []
  }
]

But I still couldn't get the packets to sync...

I came across a topic: https://github.com/pulp/pulp_python/issues/868

I assumed that these were interrelated issues. Can you confirm this? I used several options:

But I still couldn't synchronize the packages. Can you suggest a solution? pypi.org it's not available on my network, I can't use it.

At the same time, I clarified: "the mirror https://mirrors.aliyun.com/pypi/simple / fully supports the same Simple Repository API as the official PyPI "

To Reproduce

pulp python remote create   --name test-remote   --url https://mirrors.aliyun.com/pypi/   --includes '["distro"]'   --policy immediate

pulp python repository update   --name distro_local   --remote test-remote

pulp python repository sync --name distro_local

Expected behavior
I was waiting for the synchronization of packages

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported setup with the pulp python remote create, repository update, and repository sync commands, testing the listed mirror URL variants. Read the related pulp_python issue 868 and compare the sync behavior and error details. Done means identifying the cause and documenting or implementing a confirmed way to synchronize the selected distro packages from the mirror.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.