How to understand the smart-proxy selection workflow for remote-execution jobs in Red Hat Satellite 6.13?

Solution Verified - Updated -

Issue

  • How to understand the following when running a remote-execution job on a client system connected with Red Hat Satellite\Capsule :

    • Which smart-proxy is being selected for the job?
    • What all options were considered in this selection process?
    • Why an expected\unexpected smart-proxy is being selected for the job and resulting in SSH timeout?

Environment

Red Hat Satellite 6.13 and above

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content