You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have been using Pulp in on-demand mode for the Ubuntu archives (noble, noble-updates, noble-security) and only for the amd64 architecture. After several months of use, we observed that some artifacts previously used, reports 404 even though the files are present in /var/lib/pulp.
We haven't performed any resynchronizations other than the initial sync. For all repositories (noble, noble-updates, noble-security), we have created their own remote.
Pulp has been deployed in our Kubernetes cluster using the Pulp Operator. After the first occurence of the missing files we performed a redeploy.
Then I tested the archive with only noble updates in on-demand mode and created one remote version and one repository version. Then I updated the test machine with Pulp repository to get the files in Pulp repository (on-demand mode). The behavior was the same, out of 187 artifacts 38 were missing. Everything as in the first deployment.
#!/bin/bash -x
REPOSITORY_NAME='ubuntu-noble-updates-amd64'
REMOTE_NAME="${REPOSITORY_NAME}"
DISTRIBUTION_NAME="${REPOSITORY_NAME}"
SIGNING_SERVICE="deb-signing-service"
REMOTE_OPTIONS=(
--url=http://archive.ubuntu.com/ubuntu/
--distribution=noble-updates
--component=main
--component=restricted
--component=universe
--component=multiverse
--architecture=amd64
--policy on_demand
)
pulp deb remote create --name=${REMOTE_NAME} ${REMOTE_OPTIONS[@]}
pulp deb repository create --name=${REPOSITORY_NAME} --remote=${REMOTE_NAME}
pulp deb repository sync --name=${REPOSITORY_NAME}
pulp deb publication create --repository=${REPOSITORY_NAME}
pulp deb distribution create --name=${DISTRIBUTION_NAME} --base-path=${REPOSITORY_NAME} --repository=${REPOSITORY_NAME}
pulp deb remote create --name=${REMOTE_NAME} ${REMOTE_OPTIONS[@]}
pulp deb repository create --name=${REPOSITORY_NAME} --remote=${REMOTE_NAME}
pulp deb repository sync --name=${REPOSITORY_NAME}
pulp deb publication create --repository=${REPOSITORY_NAME}
pulp deb distribution create --name=${DISTRIBUTION_NAME} --base-path=${REPOSITORY_NAME} --repository=${REPOSITORY_NAME}
Additional context
I have discussed problem in the pulp_deb pulp/pulp_deb#1214
Here is the list of the files reported unavailable
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/z/zlib/zlib1g_1.3.dfsg-3.1ubuntu2.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/v/vim/xxd_9.1.0016-1ubuntu7.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/v/vim/vim_9.1.0016-1ubuntu7.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/v/vim/vim-tiny_9.1.0016-1ubuntu7.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/v/vim/vim-runtime_9.1.0016-1ubuntu7.5_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/v/vim/vim-common_9.1.0016-1ubuntu7.5_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/u/update-manager/update-manager-core_24.04.9_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/u/update-manager/python3-update-manager_24.04.9_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/s/shadow/passwd_4.13+dfsg1-4ubuntu3.2_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/p/procps/procps_4.0.4-4ubuntu3.2_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/o/openssh/openssh-sftp-server_9.6p1-3ubuntu13.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/o/openssh/openssh-server_9.6p1-3ubuntu13.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/o/openssh/openssh-client_9.6p1-3ubuntu13.5_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/s/shadow/login_4.13+dfsg1-4ubuntu3.2_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/o/open-vm-tools/open-vm-tools_12.4.5-1~ubuntu0.24.04.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/p/procps/libproc2-0_4.0.4-4ubuntu3.2_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/llvm-toolchain-18/libllvm18_18.1.3-1ubuntu1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/lvm2/libdevmapper1.02.1_1.02.185-3ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/lvm2/libdevmapper-event1.02.1_1.02.185-3ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/llvm-toolchain-18/libclang1-18_18.1.3-1ubuntu1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/llvm-toolchain-18/libclang-cpp18_18.1.3-1ubuntu1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/c/cryptsetup/libcryptsetup12_2.7.0-1ubuntu4.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/a/audit/libaudit1_3.1.2-2.1build1.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/a/audit/libaudit-common_3.1.2-2.1build1.1_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/g/git/git_2.43.0-1ubuntu7.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/g/git/git-man_2.43.0-1ubuntu7.1_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/u/util-linux/bsdutils_2.39.3-9ubuntu6.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/lvm2/dmsetup_1.02.185-3ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/l/lvm2/dmeventd_1.02.185-3ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/d/dhcpcd/dhcpcd-base_10.0.6-1ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/c/cryptsetup/cryptsetup_2.7.0-1ubuntu4.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/c/cryptsetup/cryptsetup-initramfs_2.7.0-1ubuntu4.1_all.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/c/cryptsetup/cryptsetup-bin_2.7.0-1ubuntu4.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/b/busybox/busybox-static_1.36.1-6ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/b/busybox/busybox-initramfs_1.36.1-6ubuntu3.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/b/bind9/bind9-libs_9.18.30-0ubuntu0.24.04.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/b/bind9/bind9-host_9.18.30-0ubuntu0.24.04.1_amd64.deb
Not Found: https://pulp.cloud.prz/pulp/content/ubuntu-noble-updates-amd64/pool/main/b/bind9/bind9-dnsutils_9.18.30-0ubuntu0.24.04.1_amd64.deb
The text was updated successfully, but these errors were encountered:
Version
"versions": [
{
"component": "core",
"version": "3.69.0",
"package": "pulpcore",
"module": "pulpcore.app",
"domain_compatible": true
},
{
"component": "deb",
"version": "3.4.0",
"package": "pulp_deb",
"module": "pulp_deb.app",
"domain_compatible": false
},
{
"component": "ostree",
"version": "2.4.4",
"package": "pulp-ostree",
"module": "pulp_ostree.app",
"domain_compatible": true
},
{
"component": "certguard",
"version": "3.69.0",
"package": "pulpcore",
"module": "pulp_certguard.app",
"domain_compatible": true
},
{
"component": "file",
"version": "3.69.0",
"package": "pulpcore",
"module": "pulp_file.app",
"domain_compatible": true
},
{
"component": "container",
"version": "2.22.0",
"package": "pulp-container",
"module": "pulp_container.app",
"domain_compatible": false
},
{
"component": "ansible",
"version": "0.23.1",
"package": "pulp-ansible",
"module": "pulp_ansible.app",
"domain_compatible": false
},
{
"component": "python",
"version": "3.12.5",
"package": "pulp-python",
"module": "pulp_python.app",
"domain_compatible": true
},
{
"component": "maven",
"version": "0.8.1",
"package": "pulp-maven",
"module": "pulp_maven.app",
"domain_compatible": false
},
{
"component": "rpm",
"version": "3.27.2",
"package": "pulp-rpm",
"module": "pulp_rpm.app",
"domain_compatible": true
}
],
Describe the bug
We have been using Pulp in on-demand mode for the Ubuntu archives (noble, noble-updates, noble-security) and only for the amd64 architecture. After several months of use, we observed that some artifacts previously used, reports 404 even though the files are present in /var/lib/pulp.
We haven't performed any resynchronizations other than the initial sync. For all repositories (noble, noble-updates, noble-security), we have created their own remote.
Pulp has been deployed in our Kubernetes cluster using the Pulp Operator. After the first occurence of the missing files we performed a redeploy.
Then I tested the archive with only noble updates in on-demand mode and created one remote version and one repository version. Then I updated the test machine with Pulp repository to get the files in Pulp repository (on-demand mode). The behavior was the same, out of 187 artifacts 38 were missing. Everything as in the first deployment.
I did a dB and storage check
log
We have only one version of the repository.
Now i found package
Artifact sha224 to identify file
Open pulp content (kubectl exec)
check sha
To Reproduce
Additional context
I have discussed problem in the pulp_deb pulp/pulp_deb#1214
Here is the list of the files reported unavailable
The text was updated successfully, but these errors were encountered: