Bug 2223707 - Capsule docker sync fails with 406
Summary: Capsule docker sync fails with 406
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.13.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.14.0
Assignee: satellite6-bugs
QA Contact: sganar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 15:01 UTC by Ina Panova
Modified: 2023-07-28 19:28 UTC (History)
7 users (show)

Fixed In Version: pulp-container-2.14.7-1, pulp-container-2.15.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_container issues 1329 0 None closed 406 error when syncing between pulp instances 2023-07-18 15:01:04 UTC
Red Hat Issue Tracker SAT-19027 0 None None None 2023-07-18 15:45:58 UTC

Description Ina Panova 2023-07-18 15:01:05 UTC
Description of problem:

In attempt to fix Repair API https://bugzilla.redhat.com/show_bug.cgi?id=2173671, we broke pulp-to-pulp sync aka SatServer→Capsule sync.

Capsule docker sync fails with `pulp [321cbe02e8f6495b8c21d50dece4ceee]: pulpcore.tasking.tasks:INFO: Task d018de7a-b7e3-4a1c-b028-0caa260e05dd failed (406, message='Not Acceptable', url=URL('https://ark.stackhpc.com/v2/stackhpc/centos-source-skydive-analyzer/tags/list'))`

Version-Release number of selected component (if applicable):
starting with pulp-container-2.14.6-1, pulp-container-2.15.1-1

How reproducible:


Steps to Reproduce:
1. Trigger a capsule sync
2.
3.

Actual results:
sync succeeds

Expected results:
sync fails with 406

Additional info:

Comment 1 sganar 2023-07-28 19:28:55 UTC
Verified.

Tested on Satellite 6.14.0 Snap 9.0

Steps followed: 
1. sync some repos into satellite
2. Integrate a capsule with satellite
3. Trigger a capsule sync


Observation: 
Capsule sync succeeds


Note You need to log in before you can comment on or make changes to this bug.