Synchronization of udeb packages skip architecture “all”

[alexey-orekhov]

Version

      "component": "core",
        "version": "3.23.1",
        "package": "pulpcore",
        "domain_compatible": true

        "component": "deb",
        "version": "2.20.1",
        "package": "pulp_deb",
        "domain_compatible": false

Describe the bug
Synchronization of udeb packages skip architecture “all”

To Reproduce
When I try to sync the deb.debian repository
with settings “remotes”:
http post $BASE_ADDR/pulp/api/v3/remotes/deb/apt/ name=“debian” url=“http://deb.debian.org/debian” distributions=“bullseye” architectures=“amd64” sync_udebs=true sync_installer=true

or without architectures

http post $BASE_ADDR/pulp/api/v3/remotes/deb/apt/ name=“debian” url=“http://deb.debian.org/debian” distributions=“bullseye” sync_udebs=true sync_installer=true

Pulp skips the /debian-installer/binary-all folder and doesn’t add it to the local repository

Expected behavior
When testing on VMs, udeb.all is needed to install debian over a PXE network

[quba42]

I think we had this problem with normal packages, it is possible the fix did not work for .udeb...

[alexey-orekhov]

If you are talking about this bug
#612
It looks like it's different
In my case, binary-all along the path
/pulp/content/03-04-2022-bullseye-amd64/dists/bullseye/main/debian-installer/binary-all
does not exist .
For example, if I sync amd64 architecture
http --auth admin:admin post $BASE_ADDR/pulp/api/v3/remotes/deb/apt/ name=«bullseye-amd64» url="http://ftp.debian.org/debian/" distributions="bullseye" architectures="amd64" sync_udebs=true sync_installer=true

/pulp/content/03-04-2022-bullseye-amd64/dists/bullseye/main/debian-installer/
will only contain binary-amd64

[quba42]

Are you using the verbatim publisher to publish your repo?

At least some installer files only work with the verbatim publisher. I am not sure off the top of my head if that includes installer packages.

[alexey-orekhov]

publish
http --auth admin:admin post $BASE_ADDR/pulp/api/v3/publications/deb/verbatim/ repository=/pulp/api/v3/repositories/deb/apt/461c30f2-1910-4901-9cf6-ad606af3d7d7/

distributions
http --auth admin:admin post $BASE_ADDR/pulp/api/v3/distributions/deb/apt/ name="03-04-2022-bullseye-amd64 base_path="03-04-2022-bullseye-amd64" publication=/pulp/api/v3/publications/deb/verbatim/1653112b-0631-4231-bc0f-6bd916962165/

i see udeb packages in amd64 architecture repositories, but "all" packages are missing
root@os-012080102:~# http --auth admin:admin get $BASE_ADDR/pulp/api/v3/content/deb/installer_packages/?limit=9999 | jq .results | grep 'architecture' | egrep 'amd64'

    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64",
    "architecture": "amd64"
......

root@os-012080102:~# http --auth admin:admin get $BASE_ADDR/pulp/api/v3/content/deb/installer_packages/?limit=9999 | jq .results | grep 'architecture' | egrep 'all'
empty

[quba42]

Ok, this is now definitely enough information for us to reproduce this, thanks.

[achevalet]

Any update here? It looks not possible to use PXE provisioning with Pulp because of this bug. Thanks.

[quba42]

Update: There are currently no resources to work on this, so I added a Looking_for_Contributor label.

[philnewm]

I also encountered this issue recently as I would like to PXE boot a Debian server using pulp as package source.

Started diving into the code yesterday but it will take me some time to understand how it works and why it behaves like this.
#1470 was just a shot in the dark using some help from Claude but I might redo it after understanding the context better.