Error: No declared artifact with relative path "dists/jammy/main/binary-amd64/Packages" for content "<PackageIndex (pulp_type=deb.package_index): pk=019c6d08-0eac-7872-b656-79fab1bb6b58>"

Support
1

Problem: Can not Sync due to error in subject

Expected outcome: Sync succeeds successfully

Foreman and Proxy versions: hammer (3.12.0)

  • hammer_cli_foreman (3.12.0)
  • hammer_cli_foreman_remote_execution (unknown version)
  • hammer_cli_foreman_tasks (unknown version)
  • hammer_cli_katello (1.14.3)

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

I previously had this working, but needed to rebuild the size of my disk because security repo was set to main restricted universe and multiverse.
I have tried cleaning up the database, deleting and reconfiguring the repo, but always get this same error now. I have looked at some of the other topics that are kind of similar, but don’t seem to apply directly to what I’m trying to do.

2

FWIW, I decided to try security repo again, and that seems to have worked:

image

But, I don’t understand why the other fails with:

Error: No declared artifact with relative path “dists/jammy/main/binary-amd64/Packages” for content “<PackageIndex (pulp_type=deb.package_index): pk=019c6d08-0eac-7872-b656-79fab1bb6b58>”

They appear to be identical with the exception of release/distribution

image
image712Ă—652 35.1 KB

image
image721Ă—640 33 KB

3

@matt2026 it looks like your Pulp instance has a PackageIndex in the database that is missing its related file on the filesystem. One option could be to try deleting the PackageIndex out of the database, but I’m not sure if that would have a cascading effect.

This is sounding more like a situation about repairing the relationship between Pulp’s artifact storage and the database. @quba42 might be able to give a pointer here as a maintainer of pulp-deb, but you might find it helpful to open a support thread over at Pulp’s discourse: Support - Pulp Community

4

@iballou , thanks!! I will take any help I can get. I have been fighting this for awhile. I will look into the PackageIndex in the database - is the schema out on the internet that you know of? @quba42 , if you have any ideas, I would appreciate it! I will check out the pulp discourse as well.

1 Like
5

@iballou , I think you were right, after deleting massive amounts of records from the database (a lot of it was foreign key constraints), the sync finally completed without issue. I think at least:

image
image975Ă—156 34.6 KB

1 Like
6

Glad the sync worked! If you do hit more DB issues with syncs that are harder to figure out, the Pulp Discourse is the way to go.