Sync Debian 10 Security Repo

[mambo]

Hello Community

Problem:

I would like to configure the repository for Debian 10 Security, but the sync fails with the error “No valid Release file found for ‘buster/updates’.”

This is the actual configuration:

I followed already this post: Managing deb content in Foreman issue

The main and the updates repositories are working as expected. As proposed in the mentioned post, I tried different configurations for Components like “main”, “updates/main” or just leaving it empty…

Expected outcome:

I would like to have the Debian 10 security repository syncing with incoming packages.

Foreman and Proxy plugin versions:

candlepin-4.1.7-1.el8.noarch
candlepin-selinux-4.1.7-1.el8.noarch
*****-apache-1.0-1.noarch
*****-foreman-client-1.0-1.noarch
*****-foreman-proxy-1.0-1.noarch
*****-foreman-proxy-client-1.0-1.noarch
*****-puppet-client-1.0-1.noarch
foreman-3.0.1-1.el8.noarch
foreman-cli-3.0.1-1.el8.noarch
foreman-debug-3.0.1-1.el8.noarch
foreman-dynflow-sidekiq-3.0.1-1.el8.noarch
foreman-installer-3.0.1-1.el8.noarch
foreman-installer-katello-3.0.1-1.el8.noarch
foreman-postgresql-3.0.1-1.el8.noarch
foreman-proxy-3.0.1-1.el8.noarch
foreman-release-3.0.1-1.el8.noarch
foreman-selinux-3.0.1-1.el8.noarch
foreman-service-3.0.1-1.el8.noarch
katello-4.2.0.1-1.el8.noarch
katello-certs-tools-2.8.0-1.el8.noarch
katello-client-bootstrap-1.7.7-1.el8.noarch
katello-common-4.2.0.1-1.el8.noarch
katello-debug-4.2.0.1-1.el8.noarch
katello-default-ca-1.0-1.noarch
katello-repos-4.2.0.1-1.el8.noarch
katello-selinux-4.0.2-1.el8.noarch
katello-server-ca-1.0-1.noarch
pulp-client-1.0-1.noarch
pulpcore-selinux-1.2.6-2.el8.x86_64
python3-pulp-ansible-0.9.0-2.el8.noarch
python3-pulp-certguard-1.4.0-3.el8.noarch
python3-pulp-container-2.8.1-0.2.el8.noarch
python3-pulp-deb-2.14.1-2.el8.noarch
python3-pulp-file-1.8.2-2.el8.noarch
python3-pulp-rpm-3.14.6-2.el8.noarch
python3-pulpcore-3.14.8-2.el8.noarch
qpid-proton-c-0.32.0-3.el8.x86_64
rubygem-foreman-tasks-5.1.1-1.fm3_0.el8.noarch
rubygem-foreman_fog_proxmox-0.14.0-1.fm3_0.el8.noarch
rubygem-foreman_maintain-0.8.10-1.el8.noarch
rubygem-foreman_puppet-1.0.4-1.fm3_0.el8.noarch
rubygem-foreman_remote_execution-4.7.0-1.fm3_0.el8.noarch
rubygem-hammer_cli-3.0.0-1.el8.noarch
rubygem-hammer_cli_foreman-3.0.0-1.el8.noarch
rubygem-hammer_cli_foreman_puppet-0.0.3-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el8.noarch
rubygem-hammer_cli_foreman_tasks-0.0.16-1.fm3_0.el8.noarch
rubygem-hammer_cli_katello-1.1.1-0.1.pre.master.20210804141838gitece0b63.el8.noarch
rubygem-katello-4.2.0.1-1.el8.noarch
rubygem-pulp_ansible_client-0.8.0-1.el8.noarch
rubygem-pulp_certguard_client-1.4.0-1.el8.noarch
rubygem-pulp_container_client-2.7.0-1.el8.noarch
rubygem-pulp_deb_client-2.13.0-1.el8.noarch
rubygem-pulp_file_client-1.8.1-1.el8.noarch
rubygem-pulp_python_client-3.4.0-1.el8.noarch
rubygem-pulp_rpm_client-3.13.3-1.el8.noarch
rubygem-pulpcore_client-3.14.1-1.el8.noarch
rubygem-qpid_proton-0.32.0-3.el8.x86_64
rubygem-smart_proxy_pulp-3.1.0-1.fm2_6.el8.noarch

Distribution and version:

CentOS Stream release 8
NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
CentOS Stream release 8
CentOS Stream release 8

Any help is appreciated. Regards, Michael

[quba42]

At first glance, I can’t see anything wrong with the way you entered your repo options.

I do remember I recently ensured that components with a path prefix could be entered as either updates/main or just the plain component main and either way should work. (Not sure of the top of my head if that work is already part of the release you are using).

I will try to reproduce this on my test system and get back to you.

[quba42]

Hmm. The sync appears to work fine on my test system (which does include a patch released with pulp-deb 2.16.0). You can try using Components: main instead of Components: updates/main for completeness sake, but I don’t think that will make a difference…

[mambo]

Yes, I tried already Components: main instead of Components: updates/main. Unfortunately this makes no difference.

[quba42]

Then my best guess is that this is a bug that was fixed as a side effect of Issue #7673: Support synchronization of upstream repos with minimal Release file fields including for flat repos - Debian Support - Pulp.

[mambo]

Thank you very much so far for your time looking into this. I appreciate it!

Is there a roadmap available on when I could expect this version to be released in Katello and further, is there a documented way to install this updated Version of pulp-deb already before the official release or do I have just to wait and live with it as it is?

[quba42]

The relevant fix should be automatically included in the first Katello version that uses pulpcore 3.16 (the packaging of which is being worked on now). This may be ready for Katello 4.3 @Justin_Sherrill?!

Given that the fix in question does not include any DB migrations, it might be possible to backport it to pulp_deb 2.14, and release it as part of a 2.14.2 release, which would then need to be packaged in pulpcore-packaging in order to become available to Katello 4.1. This backporting process requires some work, which I currently don’t have the time to do…

[Justin_Sherrill]

yes, we are targeting 3.16 for katello 4.3