Remote Execution Tasks Died in 'Planned' state with Foreman 1.12.4-1 & Foreman-tasks 0.7.18

Support
1

Hi,

We have installed Foreman and Foreman Remote Execution plugin with RPM
packages. When we submit a Job Invocation as 'Execute now', the Foreman's
webpage is frozen(Waiting for response), and the job's execution plan is
hung at the 'planned' state from the production.log

[foreman-tasks/dynflow] [D] ExecutionPlan
154af67e-cf68-4deb-9fb5-de510625e3c7 planning >> planned

To make foreman/foreman-task working, we have to restart the
foreman/foreman-task service manually. Then the job will be transited to
'running' state and carry on the remote execution work via foreman-proxy as
expected.(we can see the task details from
foreman-proxy's /var/log/foreman-proxy/smart_proxy_dynflow_core.log)

[foreman-tasks/dynflow] [D] ExecutionPlan
154af67e-cf68-4deb-9fb5-de510625e3c7 planned >> running

Details:

  • The services foreman/foreman-tasks are running on the Foreman server, and
    services foreman-proxy/smart_proxy_dynflow_core are running on the Foreman
    Proxy server.
  • The versions of the ruby gems on Foreman
    are(Under /opt/theforeman/tfm/root/usr/share/gems/gems/):
    ** Foreman-tasks: 0.7.18
    ** Foreman_remote_execution: 1.0.0
    ** Dynflow: 0.8.11

We have been stuck with the issue for couples of days, and are frustrated
with it.

Does anyone know how to fix the issue or have any clue? Did we forget any
specific step during the installation and configuration?

Thanks a lot in advance.

2

BTW, the Foreman/Foreman-proxy servers are CentOS release 6.5, and they are
installed via RPM packages instead of foreman-installer.

Any suggestion will be appreciated.

··· On Monday, January 9, 2017 at 9:51:14 PM UTC+8, Ming Jin wrote: > > Hi, > > We have installed Foreman and Foreman Remote Execution plugin with RPM > packages. When we submit a Job Invocation as 'Execute now', the Foreman's > webpage is frozen(Waiting for response), and the job's execution plan is > hung at the 'planned' state from the production.log > > [foreman-tasks/dynflow] [D] ExecutionPlan > 154af67e-cf68-4deb-9fb5-de510625e3c7 planning >> planned > > To make foreman/foreman-task working, we have to restart the > foreman/foreman-task service manually. Then the job will be transited to > 'running' state and carry on the remote execution work via foreman-proxy as > expected.(we can see the task details from > foreman-proxy's /var/log/foreman-proxy/smart_proxy_dynflow_core.log) > > [foreman-tasks/dynflow] [D] ExecutionPlan > 154af67e-cf68-4deb-9fb5-de510625e3c7 planned >> running > > Details: > * The services foreman/foreman-tasks are running on the Foreman server, > and services foreman-proxy/smart_proxy_dynflow_core are running on the > Foreman Proxy server. > * The versions of the ruby gems on Foreman > are(Under /opt/theforeman/tfm/root/usr/share/gems/gems/): > ** Foreman-tasks: 0.7.18 > ** Foreman_remote_execution: 1.0.0 > ** Dynflow: 0.8.11 > > We have been stuck with the issue for couples of days, and are frustrated > with it. > > Does anyone know how to fix the issue or have any clue? Did we forget any > specific step during the installation and configuration? > > Thanks a lot in advance. > > >
3

An update, we managed to make remote execution work after reinstalling the
Foreman server with Foreman-Installer.

So I guess there were some setting we missed the last time…

··· On Monday, January 9, 2017 at 10:42:30 PM UTC+8, Ming Jin wrote: > > BTW, the Foreman/Foreman-proxy servers are CentOS release 6.5, and they > are installed via RPM packages instead of foreman-installer. > > Any suggestion will be appreciated. > > > On Monday, January 9, 2017 at 9:51:14 PM UTC+8, Ming Jin wrote: >> >> Hi, >> >> We have installed Foreman and Foreman Remote Execution plugin with RPM >> packages. When we submit a Job Invocation as 'Execute now', the Foreman's >> webpage is frozen(Waiting for response), and the job's execution plan is >> hung at the 'planned' state from the production.log >> >> [foreman-tasks/dynflow] [D] ExecutionPlan >> 154af67e-cf68-4deb-9fb5-de510625e3c7 planning >> planned >> >> To make foreman/foreman-task working, we have to restart the >> foreman/foreman-task service manually. Then the job will be transited to >> 'running' state and carry on the remote execution work via foreman-proxy as >> expected.(we can see the task details from >> foreman-proxy's /var/log/foreman-proxy/smart_proxy_dynflow_core.log) >> >> [foreman-tasks/dynflow] [D] ExecutionPlan >> 154af67e-cf68-4deb-9fb5-de510625e3c7 planned >> running >> >> Details: >> * The services foreman/foreman-tasks are running on the Foreman server, >> and services foreman-proxy/smart_proxy_dynflow_core are running on the >> Foreman Proxy server. >> * The versions of the ruby gems on Foreman >> are(Under /opt/theforeman/tfm/root/usr/share/gems/gems/): >> ** Foreman-tasks: 0.7.18 >> ** Foreman_remote_execution: 1.0.0 >> ** Dynflow: 0.8.11 >> >> We have been stuck with the issue for couples of days, and are frustrated >> with it. >> >> Does anyone know how to fix the issue or have any clue? Did we forget any >> specific step during the installation and configuration? >> >> Thanks a lot in advance. >> >> >>