Remote execution fails with "Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - Could not use any Capsule. Consider configuring remote_execution_global_proxy or remote_execution_fallback_proxy in settings" in Red Hat Satellite 6.

Solution Verified - Updated -

Environment

  • Red Hat Satellite 6.2.x

Issue

  • Remote execution fails with "Failed to initialize command: Dynflow::ExecutionPlan::Steps::Error - Could not use any Capsule. Consider configuring remote_execution_global_proxy or remote_execution_fallback_proxy in settings" on all the hosts.

Resolution

  • Assign proper location and organization to the capsule server.
  • Following command can be used to get capsule info # hammer capsule info --id <ID>.
# hammer capsule info --id 1
Id:            1
Name:          host1.example.com
URL:           https://host1.example.com:9090
Features:
    Pulp
    Puppet
    Puppet CA
    Dynflow
    Discovery
    Openscap
    SSH
Locations:
    Pune
Organizations:
    Red Hat
Created at:    2017/06/30 17:41:51
Updated at:    2017/06/30 17:41:52

Root Cause

  • The location was not assigned to the capsule server.

Diagnostic Steps

  • Capsule info of the affected capsule server:
# hammer capsule info --id 1
Id:            1
Name:          host1.example.com
URL:           https://host1.example.com:9090
Features:
    Pulp
    Puppet
    Puppet CA
    Dynflow
    Discovery
    Openscap
    SSH
Organizations:
    Red Hat
Created at:    2017/06/30 17:41:51
Updated at:    2017/06/30 17:41:52

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.