Consolidated Troubleshooting Article for Red Hat Satellite 6.x Remote Execution Issues
Updated
General Issues
- Common configuration and troubleshooting of Remote Execution with Red Hat Satellite 6
- Job running on multiple content hosts show all pending in Satellite's web UI even though the job is actually running
- Using the
host-registration generate-commandwith--setup-remote-executionon Red Hat Satellite 6.x drops the sudoers file with incorrect permissions - Remote execution tasks using scripts fail, whereas remote execution tasks using Ansible roles/playbooks complete successfully for the same host(s)
- Remote execution fails with the error 'Failed to establish connection to remote host, exit code: 255'
- Satellite is not processing remote execution tasks
- Remote Execution fails with error 'Error initializing command - RuntimeError Could not establish connection to remote host using any available authentication method, tried publickey'
- Remote execution in Satellite 6 fails with "su: Authentication failure"
- Remote execution in Satellite 6 fails with "Failed to execute script on remote machine, exit code: 126 "
- Remote execution on Red Hat Satellite 6 fails with: Unmatched ' " '
- Remote execution fails after upgrading Satellite to 6.11 with error "Unable to create directory on remote system" and "exit code: 255"
- Unable to plan Ansible tasks with large inventories in Satellite
- Remote Execution job fails with error "no such identity: .ssh/id_rsa_foreman_proxy" in Red Hat Satellite 6
- Remote execution jobs are failing with error "SocketError getaddrinfo: Name or service not known" in Red Hat Satellite 6.
- [Satellite 6] Remote jobs fail with 'The task has been cancelled. Is katello-agent installed and goferd running on the Host?'
- Alternative to Goferd, Katello-Host-Tools and Remote Execution
- Red Hat Satellite 6: Remote Execution is getting failed with error "Error initializing command: Net::SSH::ConnectionTimeout – Net::SSH::ConnectionTimeout".
- [Satellite6] Remote Execution fail with FIPS enabled on client
- Package installation with remote execution is failing with error in Red Hat Satellite 6.
- StandardError - The task could not be started within the maintenance window - While running remote execution job Through Red Hat Satellite 6 on Host Collections.
- Remote Execution Jobs using non-root user are failing with Error "Failed to initialize: Dynflow::ExecutionPlan::Steps::Error - Job execution failed"
- Remote execution jobs is failing with error "Net::SSH::ConnectionTimeout" on Red Hat Satellite
- Remote Execution job on Red Hat Satellite with large batch of hosts fails with Foreman::Exception: The capsule task failed.
- Remote execution fails with error: Authentication failed for user root@1.2.3.4
- Running remote execution Ansible jobs fails with error
Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user root@client.example.comon Red Hat Satellite 6 - Remote Execution fails with message Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user root@client.example.com in Red Hat Satellite
- Satellite remote execution job to external Capsule fails with Error initializing command Net::SSH::AuthenticationFailed - Authentication failed for user root@capsule01.example.org
- Remote Execution fails from Capsule server with message Error initializing command: Net::SSH::AuthenticationFailed - Authentication failed for user root@client.example.com in Red Hat Satellite 6.5.
- Remote execution fails with "Authentication failed for user root@client_hostname" even though keys are correctly copied
- Scheduled future Remote Jobs stays in Queued state past set time.
- foreman_tasks:cleanup leaves jobs in state 'queued'
- I need a hammer (CLI) command that will cancel jobs
- Ansible package installation job through Red Hat Satellite 6 fails
- Red Hat Satellite 6.4 fails to run ansible-based remote execute commands when enrolled in IdM domain
- Satellite fails to execute ansible commands when connected to ipa server
- [Satellite 6]Running ansible job on multiple hosts succeeds while on single host fails
- REX jobs failing with Error initializing command: Errno::ECONNREFUSED - Connection refused.
- Remote Execution jobs invoked around 3am get stuck forever
- Scheduled remote execution jobs by hammer command are always getting executed as per UTC timezone in Red Hat Satellite 6
- [Satellite 6.11] REX job fails with "Initialization error: RestClient::NotFound - 404 Not FoundError loading data from Capsule: NoMethodError - undefined method `code' for "404 Not Found"
- Running an Remote Execution Job from Satellite, report: "[WARNING]: sftp transfer mechanism failed on [host.fqdn]. Use ANSIBLE_DEBUG=1\r\n to see detailed information\n"
- Running Remote Execution Job from Satellite, fails with: "Initialization error: RestClient::NotFound - 404 Not Found"
- Ansible facts are not updated after job execution
- Remote execution job fails with error "Failed to initialize: RuntimeError - The only applicable proxy capsule.example.com is down" in Red Hat satellite 6
- Any remote execution job on RHEL 7.x fails with "Error initializing command: RuntimeError - Could not establish connection to remote host using any available authentication method, tried publickey" in Red Hat Satellite 6
- Remote execution job failed with "Error initializing command: RuntimeError - Could not establish connection to remote host using any available authentication method, tried publickey" in Red Hat Satellite 6
Issues related to Ansible Roles/Playbooks
- Ansible playbook task unable to enable callback plugin per-template.
[WARNING]: Callback disabled by environment. Disabling the Foreman callbackwhile running Ansible playbooks via remote execution on Red Hat Satellite 6.x
How To
- How to select multiple hosts in the Remote Execution Job invocation wizard on Red Hat Satellite 6.x?
- How to change the working directory of the remote execution plugin in Red Hat Satellite 6?
- How to setup Remote Execution using non-root users with password?
- How to setup Remote Execution using non-root user on RHEL systems connected to Red Hat Satellite 6?
- What is the minimal amount of privileges granted to sudo user for Remote Execution feature in Satellite6?
- Configure the satellite remote execution to use SSH key other than foreman-proxy SSH key
- [Satellite 6] How to copy foreman-proxy user public ssh key to many client systems for Remote Execution
- How to change ssh keys of foreman-proxy user in Red Hat Satellite 6
- [Satellite 6] How to generate new SSH keys for Remote Execution feature.
- How to perform Remote Execution in Red Hat Satellite 6 using Kerberos.
- Filter hosts registered to Red Hat Satellite 6.4 as per the status of job executed.
- How to remove job-invocation using hammer cli?
- How to print the complete input of a REX job using the hammer command line on Red Hat Satellite 6?
- How to specify the desired Red Hat Satellite Capsule to be used for Remote Execution (REX)?
- Iist all subnets that use a specific capsule for remote execution on Red Hat Satellite 6.
- How to setup Remote Execution for Satellite 6
- Encryption of Sudo Password for Remote Execution on Satellite 6
- How to Prefer registered through Capsule for remote execution on client system registered to satellite or capsule server
Q & A
- What permissions to be set on /var/tmp/foreman-proxy/foreman-ssh-cmd-*/script for remote execution?
- What happens to the scheduled remote execution jobs when Satellite is down?
- What parameters should be set to run Remote Jobs in Red Hat Satellite 6 to prevent overload of system resources?
SBR
Product(s)
Article Type