Remote Execution Plugin V0.0.7 from the stable Repo

Hi Marek & Ivan,

sorry to bother you again, I have upgraded yesterday the Remote Execution
Plugin to Version 0.0.7 from the stable Repo, now I have a lot of problems!
The Main Issue is described below, is there maybe any special setup
somewhere required? I tried all Options from Menue Administer =>
RemoteExecution => Remote Execution Proxy, but it did not help…

Issue1: Remote Execution does not longer work
RestClient::ResourceNotFound: 404 Resource Not Found
undefined method `live_output' for nil:NilClass (NoMethodError)
Could not use any proxy. Consider configuring remote_execution_global_proxy
or remote_execution_fallback_proxy in settings

Issue2: Template execution is asking for input even if is not marked as
"required" in Job Templates

I

ssue3: Schedule Future Job - confusing time for UTC & CEST/GMT+xMy
Katello/Foreman RPMs:

[root@katello yum.repos.d]# rpm -qa | grep -i foreman | sort
-nforeman-1.9.2-1.el7.noarchforeman-compute-1.9.2-1.el7.noarchforeman-debug-1.9.2-1.el7.noarchforeman-ec2-1.9.2-1.el7.noarchforeman-gce-1.9.2-1.el7.noarchforeman-libvirt-1.9.2-1.el7.noarchforeman-ovirt-1.9.2-1.el7.noarchforeman-postgresql-1.9.2-1.el7.noarchforeman-proxy-1.9.2-1.el7.noarchforeman-release-1.9.2-1.el7.noarchforeman-selinux-1.9.2-1.el7.noarchforeman-vmware-1.9.2-1.el7.noarchkatello.cesystems.at-foreman-client-1.0-1.noarchkatello.cesystems.at-foreman-proxy-1.0-1.noarchkatello.cesystems.at-foreman-proxy-client-1.0-1.noarchruby193-rubygem-foreman_bootdisk-6.0.0-1.el7.noarchruby193-rubygem-foreman_discovery-4.0.0-1.fm1_9.el7.noarchruby193-rubygem-foreman_docker-1.4.1-1.fm1_9.el7.noarchruby193-rubygem-foreman_gutterball-0.0.1-1.201507061443gitb9974c7.git.0.64e9626.el7.noarchruby193-rubygem-foreman_hooks-0.3.8-1.el7.noarchruby193-rubygem-foreman_openscap-0.4.3-1.fm1_9.el7.noarchruby193-rubygem-foreman_remote_execution-0.0.7-1.fm1_9.el7.noarchruby193-rubygem-foreman-tasks-0.7.6-1.fm1_9.el7.noarchruby193-rubygem-foreman-tasks-doc-0.7.6-1.fm1_9.el7.noarchrubygem-foreman_scap_client-0.1.1-1.el7.noarchrubygem-hammer_cli_foreman-0.3.0-1.el7.noarchrubygem-hammer_cli_foreman_bootdisk-0.1.3-1.el7.noarchrubygem-hammer_cli_foreman_docker-0.0.3-2.el7.noarchrubygem-hammer_cli_foreman_tasks-0.0.7-1.el7.noarch[root@katello
yum.repos.d]# rpm -qa | grep -i proxy | sort
-nforeman-proxy-1.9.2-1.el7.noarchkatello.cesystems.at-foreman-proxy-1.0-1.noarchkatello.cesystems.at-foreman-proxy-client-1.0-1.noarchlibproxy-0.4.11-6.el7.x86_64rubygem-smart_proxy_dynflow-0.0.3-1.el7.noarchrubygem-smart_proxy_openscap-0.4.1-1.el7.noarchrubygem-smart_proxy_pulp-1.0.1-2.el7.noarchrubygem-smart_proxy_remote_execution_ssh-0.0.5-1.el7.noarc
I
hope you can assist me, because this is blocking me for further testing…

thanks,
Christian

Hello

sending updates below in text after chat on IRC

> Issue1: Remote Execution does not longer work
> RestClient::ResourceNotFound: 404 Resource Not Found
> undefined method `live_output' for nil:NilClass (NoMethodError)
> Could not use any proxy. Consider configuring remote_execution_global_proxy
> or remote_execution_fallback_proxy in settings

Caused by older version of rubygem-smart_proxy_dynflow, 0.0.4 is required.
Seems we failed to spot this dependency.

> Issue2: Template execution is asking for input even if is not marked as
> "required" in Job Templates

This was already reported as [1] and being actively worked on.

> Issue3: Schedule Future Job - confusing time for UTC & CEST/GMT+x*My
> Katello/Foreman RPMs:

Could you please create a new redmine issue for this and describe a bit more,
what's confusing and what would be desired state?

Thank you

[1] Bug #12064: ssh package provider is requireing unneeded input - Foreman Remote Execution - Foreman

··· -- Marek

Hi Marek,

maybe you can help once more, my Future Time Remote Execution Jobs are not
started, an example (Evaluated yesterday at: 2015-10-07 13:12:29 UTC, Job
set to execute at 2015-10-07 18:00:00 UTC)
The Result is that nothing happend, do you have any idea? Where can I start
my debugging, is there anything I can look for in Logs, DB or so on? My
Server is in CEST, so the 2 hours difference to UTC could not be the
problem…

thanks,
Christian

> Hello
>
> sending updates below in text after chat on IRC
>
> > Issue1: Remote Execution does not longer work
> > RestClient::ResourceNotFound: 404 Resource Not Found
> > undefined method `live_output' for nil:NilClass (NoMethodError)
> > Could not use any proxy. Consider configuring remote_execution_global_proxy
> > or remote_execution_fallback_proxy in settings
>
> Caused by older version of rubygem-smart_proxy_dynflow, 0.0.4 is required.
> Seems we failed to spot this dependency.

The package is there, just update it. I'll do a new release with the
right dependencies as soon as the other issue below is fixed as well.

··· On Wed, Oct 07, 2015 at 11:21:03AM +0200, Marek Hulan wrote:

Issue2: Template execution is asking for input even if is not marked as
"required" in Job Templates

This was already reported as [1] and being actively worked on.

Issue3: Schedule Future Job - confusing time for UTC & CEST/GMT+x*My
Katello/Foreman RPMs:

Could you please create a new redmine issue for this and describe a bit more,
what’s confusing and what would be desired state?

Thank you

[1] Bug #12064: ssh package provider is requireing unneeded input - Foreman Remote Execution - Foreman


Marek


You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Best Regards,

Stephen Benjamin
Red Hat Engineering

Update from IRC:

working on the fix, there seems to be some issue with not spawning an
executor for delayed executions
you can watch the progress at Bug #12088: When executor with a role of delayed executor exits in a non-standard way, new executor would take over the job - foreman-tasks - Foreman