Actions
Issue #8828
closed
Synchronizing buster/updates succeeds but does not download any packages
Start date:
Due date:
Estimated time:
Severity:
3. High
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Reproducer remote:
REMOTE_HREF=$(http post "${BASE_ADDR}"/pulp/api/v3/remotes/deb/apt/ name="${ENTITIES_NAME}" distributions="buster/updates" components="main" architectures="amd64" url="https://deb.debian.org/debian-security/" | jq -r '.pulp_href')
Result: The sync is successful, but the repo version contains no packages.
First reported here: https://community.theforeman.org/t/subscription-manager-for-debian-ubuntu-on-apt-atix-de/20667/43?u=quba42
Updated by quba42 over 3 years ago
If I do NOT specify components=main in the remote, then I see packages being downloaded.
Updated by quba42 over 3 years ago
Hypothesis: It could be related to the fact that the component is prefixed in the Release file (updates/main) which might throw it out during filtering. If so, then the "plain component" needs to be used instead.
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Updated by quba42 over 3 years ago
- Sprint/Milestone changed from Katello to 2.13.0
Added by quba42 over 3 years ago
Updated by quba42 over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset dfb0cf6358ef36a2e57db3c761a0cd4558e21d4b.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Consider that release file components may not be plain components
Closes #8828 https://pulp.plan.io/issues/8828
When creating an intersection between the release file components and the components from the remote, we need to consider the special case, where the release file components have a path prefix, but those from the remote do not!