Trying to setup remote execution to apply applicable errata to hosts in
Katell 3.0 (latest RC), and I'm getting the above error when I try to run
the job. I am able to execute jobs on the remote server, so the plugin
itself appears to be working correctly. Am I missing anything in my config?
I checked the job template, but I don't see anywhere where I may need to
create a mapping.
> From: "salman b" <namlas@gmail.com>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Sent: Tuesday, June 7, 2016 2:16:19 PM
> Subject: [foreman-users] ERF42-5962 [Foreman::Exception]: No template mapped to feature Katello: Install Errata
>
> Hi all,
>
> Trying to setup remote execution to apply applicable errata to hosts in
> Katell 3.0 (latest RC), and I'm getting the above error when I try to run
> the job. I am able to execute jobs on the remote server, so the plugin
> itself appears to be working correctly. Am I missing anything in my config?
>
> I checked the job template, but I don't see anywhere where I may need to
> create a mapping.
>
> Here is the full trace:
> http://pastebin.com/aCAWkgwV
You would map the templates under Administer / Remote Execution Features. This was a bug
that should be fixed in the next release of remote execution so we'll set up the mapping
automatically for you.
···
On Tue, Jun 7, 2016 at 4:30 PM, Stephen Benjamin wrote:
----- Original Message -----
From: “salman b” namlas@gmail.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Tuesday, June 7, 2016 2:16:19 PM
Subject: [foreman-users] ERF42-5962 [Foreman::Exception]: No template
mapped to feature Katello: Install Errata
Hi all,
Trying to setup remote execution to apply applicable errata to hosts in
Katell 3.0 (latest RC), and I’m getting the above error when I try to run
the job. I am able to execute jobs on the remote server, so the plugin
itself appears to be working correctly. Am I missing anything in my
config?
I checked the job template, but I don’t see anywhere where I may need to
create a mapping.
You would map the templates under Administer / Remote Execution Features.
This was a bug
that should be fixed in the next release of remote execution so we’ll set
up the mapping
automatically for you.