Bug 1583481

Summary: action "Run ansible roles" fails
Product: Red Hat Satellite Reporter: Martin Korbel <mkorbel>
Component: Ansible - Configuration ManagementAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: cwelton, dlobatog, jhutar, mhulan, sbadhwar
Target Milestone: 6.4.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman_ansible-2.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 18:54:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1449011    

Description Martin Korbel 2018-05-29 06:03:37 UTC
Description of problem:
When I try to run "Run ansible roles" for apply assigned roles, I get this error message

"ERF42-5962 [Foreman::Exception]: No template mapped to feature Ansible: Run host roles"

Version-Release number of selected component (if applicable):
ansible-2.5.2-1.el7ae.noarch
tfm-rubygem-foreman_ansible-2.1.2.0.1-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.0.2-1.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
ansiblerole-insights-client-1.5-1.el7sat.noarch

How reproducible:
100%

Steps to Reproduce:
1. Import role to Sat6.4
2. Assign this role to host
3. Press button "Run ansible roles"

Actual results:
"ERF42-5962 [Foreman::Exception]: No template mapped to feature Ansible: Run host roles"

Expected results:
No error; the role will be apply to host

Additional info:

Comment 1 Martin Korbel 2018-05-29 06:19:29 UTC
The list of job templates is empty. All templates are missing.

tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.6-2.el7sat.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.2-1.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.5.2-2.el7sat.noarch
rubygem-smart_proxy_remote_execution_ssh-0.2.0-2.el7sat.noarch

tfm-rubygem-angular-rails-templates-1.0.2-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_templates-0.1.0-1.el7sat.noarch
tfm-rubygem-foreman_templates-6.0.1-1.el7sat.noarch

Comment 3 Daniel Lobato Garcia 2018-05-30 13:45:19 UTC
Created redmine issue http://projects.theforeman.org/issues/23742 from this bug

Comment 4 Daniel Lobato Garcia 2018-05-30 13:46:24 UTC
Setting as triaged, the issue seems to be that the templates are not in *all* organizations by default, which should be the default after importing them.

Comment 5 Marek Hulan 2018-06-12 05:39:52 UTC
I do agree this is a blocker, not sure why the flag was not set. I see all three acks. I don't have perms to set it.

Comment 6 Satellite Program 2018-06-12 06:06:08 UTC
Upstream bug assigned to mhulan

Comment 7 Satellite Program 2018-06-12 06:06:11 UTC
Upstream bug assigned to mhulan

Comment 8 Marek Hulan 2018-06-12 06:14:53 UTC
*** Bug 1589931 has been marked as a duplicate of this bug. ***

Comment 9 Jan Hutař 2018-06-13 09:15:34 UTC
In 6.3, Job templates have organization set correctly

Comment 10 Jan Hutař 2018-06-13 09:15:59 UTC
*** Bug 1589988 has been marked as a duplicate of this bug. ***

Comment 11 Satellite Program 2018-06-14 14:06:00 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23891 has been resolved.

Comment 12 Martin Korbel 2018-06-26 11:26:45 UTC
VERIFIED on Sat6.4#9

Reproducer by comment #0

> rpm -qa | grep  foreman_ansible
tfm-rubygem-foreman_ansible_core-2.1.0-1.el7sat.noarch
tfm-rubygem-foreman_ansible-2.2.0-1.el7sat.noarch

Comment 14 Bryan Kearney 2018-10-16 18:54:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927