pulp / pulp/pulpcore

Repository version errors : Path errors found. Paths are duplicated

Open
#2,074 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Database Issue
Dominant language
Python
Stars
598
Forks
168
Avg merge
1d 4h
Merged PRs (30d)
86

Description

Author: rgp (rgp)

Redmine Issue: 9661, https://pulp.plan.io/issues/9661


Hi,
I'm seeing the following errors when syncing ubuntu bionic repositories:

1. grep duplicated production.log-20220105
2022-01-05T03:01:19 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/stable/Release,dists/stable/InRelease,dists/stable/Release.gpg,dists/stable/main/binary-amd64/Packages,dists/stable/main/binary-amd64/Packages.gz,dists/stable/main/binary-amd64/Release
2022-01-05T03:02:09 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/stable/Release,dists/stable/InRelease,dists/stable/Release.gpg,dists/stable/main/binary-amd64/Packages.gz,dists/stable/main/binary-amd64/Release,dists/stable/main/binary-amd64/Packages
2022-01-05T03:02:16 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/bionic/Release,dists/bionic/InRelease,dists/bionic/Release.gpg,dists/bionic/multiverse/binary-amd64/Release,dists/bionic/multiverse/binary-amd64/Packages,dists/bionic/multiverse/binary-amd64/Packages.gz
2022-01-05T03:02:24 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/bionic/InRelease,dists/bionic/Release.gpg,dists/bionic/Release,dists/bionic/main/binary-amd64/Packages,dists/bionic/main/binary-amd64/Packages.gz
2022-01-05T03:06:24 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/bionic/main/binary-armhf/Packages,dists/bionic/main/binary-armhf/Packages.gz,dists/bionic/main/binary-arm64/Packages,dists/bionic/main/binary-arm64/Packages.gz,dists/bionic/InRelease,dists/bionic/Release,dists/bionic/Release.gpg,dists/bionic/main/binary-armel/Packages,dists/bionic/main/binary-armel/Packages.gz,dists/bionic/main/binary-amd64/Packages,dists/bionic/main/binary-amd64/Packages.gz,dists/bionic/main/binary-s390x/Packages,dists/bionic/main/binary-s390x/Packages.gz,dists/bionic/main/binary-i386/Packages,dists/bionic/main/binary-i386/Packages.gz,dists/bionic/main/binary-ppc64el/Packages,dists/bionic/main/binary-ppc64el/Packages.gz
2022-01-05T03:06:49 [E|bac|4a143c87] Repository version errors : Path errors found. Paths are duplicated: dists/stable/main/binary-i386/Packages,dists/stable/main/binary-i386/Packages.gz,dists/stable/main/binary-i386/Release,dists/stable/main/binary-aarch64/Packages,dists/stable/main/binary-aarch64/Packages.gz,dists/stable/main/binary-aarch64/Release,dists/stable/InRelease,dists/stable/Release,dists/stable/Release.gpg,dists/stable/main/binary-amd64/Packages,dists/stable/main/binary-amd64/Packages.gz,dists/stable/main/binary-amd64/Release,dists/stable/main/binary-arm64/Packages,dists/stable/main/binary-arm64/Packages.gz,dists/stable/main/binary-arm64/Release

Not sure if this is related, but I also encountered the following error before these:

deadlock detected
DETAIL:  Process 531 waits for ShareLock on transaction 24995797; blocked by process 524.
Process 524 waits for ShareLock on transaction 24995798; blocked by process 531.
HINT:  See server log for query details.
CONTEXT:  while updating tuple (7388,19) in relation "core_artifact"

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

No source file, test, or entry point is named. Start by tracing the repository-sync path that emits the duplicate-path errors, then inspect the PostgreSQL transaction involving the core_artifact relation to determine whether the deadlock and duplication are related. Done means the cause is confirmed and the affected failure has a reproducible regression test or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.