Problem:
I am trying to run a simple echo hi
or cat /etc/hosts
command from foreman web UI. I am getting the following errro in foreman_tasks section:
Failed to initialize: Dynflow::ExecutionPlan::Steps::Error - ERF42-3837 [Foreman::Exception]: The smart proxy task b38453f0-06e2-44a9-9346-4b84deecda38 failed.
Error initializing command: IOError - closed stream
Errors:
ERF42-3837 [Foreman::Exception]: The smart proxy task b38453f0-06e2-44a9-9346-4b84deecda38 failed.
Ruby is kind of Greek to me and any help would be appreciated.
Note that I installed all the packages required for remote execution as per Foreman :: Plugin Manuals as I already had existing foreman installation. I created SSH keys as mentioned and copied that to my client.
Expected outcome:
Remote exeuction should work.
Foreman and Proxy versions:
[root@foremankatellodemo .ssh]# rpm -qa | grep foreman
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-2.el7.noarch
foremankatellodemo.example.com-foreman-client-1.0-1.noarch
foremankatellodemo.example.com-puppet-client-1.0-1.noarch
tfm-rubygem-hammer_cli_foreman-0.10.2-1.el7.noarch
foremankatellodemo.example.com-foreman-proxy-client-1.0-1.noarch
foreman-debug-1.15.6-1.el7.noarch
foreman-selinux-1.15.6-1.el7.noarch
foreman-1.15.6-1.el7.noarch
foreman-postgresql-1.15.6-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-5.el7.noarch
foremankatellodemo.example.com-qpid-router-server-1.0-1.noarch
foremankatellodemo.example.com-tomcat-1.0-1.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7.noarch
foreman-installer-1.15.6-2.el7.noarch
foreman-release-scl-3-1.el7.noarch
tfm-rubygem-foreman-tasks-core-0.1.8-1.fm1_15.el7.noarch
foreman-compute-1.15.6-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.12-1.fm1_15.el7.noarch
foremankatellodemo.example.com-apache-1.0-1.noarch
foremankatellodemo.example.com-qpid-router-client-1.0-1.noarch
foreman-cli-1.15.6-1.el7.noarch
foremankatellodemo.example.com-qpid-client-cert-1.0-1.noarch
tfm-rubygem-foreman_remote_execution-1.3.7-1.fm1_15.el7.noarch
tfm-rubygem-foreman_docker-3.2.1-1.fm1_15.el7.noarch
foremankatellodemo.example.com-foreman-proxy-1.0-1.noarch
foremankatellodemo.example.com-qpid-broker-1.0-1.noarch
foreman-proxy-1.15.6-1.el7.noarch
foreman-installer-katello-3.4.5-1.el7.noarch
tfm-rubygem-foreman-tasks-0.9.6-1.fm1_15.el7.noarch
foreman-release-1.15.6-1.el7.noarch
[root@foremankatellodemo .ssh]#
Foreman and Proxy plugin versions:
[root@foremankatellodemo .ssh]# foreman-rake plugin:list
Collecting plugin information
Foreman plugin: bastion, 5.1.1, Eric D Helms and Walden Raines, Bastion provides a UI library of AngularJS based components designed to integrate and work with Foreman.
Foreman plugin: foreman-tasks, 0.9.6, Ivan NeÄŤas, The goal of this plugin is to unify the way of showing task statuses across the Foreman instance.
It defines Task model for keeping the information about the tasks and Lock for assigning the tasks
to resources. The locking allows dealing with preventing multiple colliding tasks to be run on the
same resource. It also optionally provides Dynflow infrastructure for using it for managing the tasks.
Foreman plugin: foreman_docker, 3.2.1, Daniel Lobato, Amos Benari, Provision and manage Docker containers and images from Foreman.
Foreman plugin: foreman_remote_execution, 1.3.7, Foreman Remote Execution team, A plugin bringing remote execution to the Foreman, completing the config management functionality with remote management functionality.
Foreman plugin: katello, 3.4.5, N/A, Content and Subscription Management plugin for Foreman
[root@foremankatellodemo .ssh]#
Other relevant data:
Cannot put production.log in this post. That’s coming.
Any help is appreciated. Thanks folks.