Bug 2293102

Summary: Undercloud registry serves tgz files with content-type:application/octet-stream
Product: Red Hat OpenStack Reporter: Eric Nothen <enothen>
Component: tripleo-ansibleAssignee: Lukas Bezdicka <lbezdick>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: high    
Version: 16.2 (Train)CC: drosenfe, lbezdick, mariel, pweeks
Target Milestone: z4Keywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tripleo-ansible-3.3.1-17.1.20240920151437.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-21 09:41:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Nothen 2024-06-19 15:25:45 UTC
Description of problem:

After an upgrade to Satellite 6.14, the undercloud registry cannot be used as repository of type docker anymore.

Version-Release number of selected component (if applicable):
RHOSP 16.2 and 17.1
Satellite > 6.13

How reproducible:
Always reproducible

Steps to Reproduce:
1. Configure the undercloud to serve images
2. Configure at least one repository of type docker in Satellite, pointing to the undercloud registry. Make sure download policy is set to "Immediate" (which is what actually downloads the blobs).
3. Synchronize repository

Actual results:
Repository sync fails with the following error:
~~~
406, message='Not Acceptable', url=URL('http://192.168.122.190:8787/v2/keller-prod-osp_17_1_cv-rhosp17_containers-nova-compute/blobs/sha256:3d87f00fc2bc8131c8336792f0143b3ce4b4739e281cceca191bfd04cd7a8d21')
~~~

Expected results:
Satellite is able to download blobs from the undercloud registry.

Additional info:

See analysis from Satellite support / engineering here:

https://issues.redhat.com/browse/SAT-25848

Comment 12 errata-xmlrpc 2024-11-21 09:41:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHOSP 17.1.4 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2024:9974