Problem Statement

When configuring Satellite using an HTTP Proxy, the proxy in question must be configured to enable both TCP and UDP traffic.  cdn.redhat.com performs an initial handshake using a TCP connection, then performs a transition to UDP traffic.

If an HTTP proxy is configured with TCP only, content synchronization will initiate but fail to begin downloading content, causing it to timeout or freeze.

User Experience & Workflow

The Satellite documentation provides a clear workflow for leveraging an HTTP proxy, but does not contain any requirements for the HTTP proxy.  This can lead to excessive troubleshooting before identifying the source issue.

Requirements

Documentation updates adding clarification that both TCP and UDP traffic are required over any configured HTTP proxy for content downloads through cdn.redhat.com

Business Impact

Possible reduction in support ticket requests after clarification added.