I have a partner (Odigos) with a weird situation with the registry.connect.redhat.com proxy.

Support case: 04054818

Quick précis:  Can our proxy pull images that are behind a partner's proxy?This partner has a Google Artifacts-based registry behind their own proxy, and is using our proxy to distribute the image.  The registry behind their proxy is wide open (for debugging purposes).  Partner (and I) can pull directly from the open registry, but attempts to pull through our proxy get 502 Bad Gateway errors.Image as served by our proxy: registry.connect.redhat.com/odigos/odigos-scheduler-ubi9:v1.0.149.

Log:

podman pull registry.connect.redhat.com/odigos/odigos-scheduler-ubi9:v1.0.149 
Trying to pull registry.connect.redhat.com/odigos/odigos-scheduler-ubi9:v1.0.149... Error: initializing source [docker://registry.connect.redhat.com/odigos/odigos-scheduler-ubi9:v1.0.149]: reading manifest v1.0.149 in registry.connect.redhat.com/odigos/odigos-scheduler-ubi9: received unexpected HTTP status: 502 Bad Gateway

Trying this in their direct registry works.

Their Direct registry: registry.odigos.io/odigos-scheduler-ubi9:v1.0.149
 
Log:

podman pull registry.odigos.io/odigos-scheduler-ubi9:v1.0.149 Trying to pull registry.odigos.io/odigos-scheduler-ubi9:v1.0.149... Getting image source signatures Copying blob 70176e7455ec done [...]

@Adam looked at it for me and found that the manifest is apparently not in the same location as the container image data.

Their direct registry is a Google Artifact Registry.

Thread link in Slack: https://redhat-internal.slack.com/archives/C7WH69HCY/p1739215504468569