Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1386864

Summary: Unable to run Ansible roles on hosts
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: bkearney, dlobatog, lpramuk, mhulan, sthirugn
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:12:14 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:
Attachments:
Description Flags
task failure none

Description sthirugn@redhat.com 2016-10-19 17:59:52 UTC 
Description of problem:
Unable to run Ansible roles on hosts

Version-Release number of selected component (if applicable):

# rpm -qa | grep satellite
satellite-installer-6.3.0-1.el7sat.noarch
satellite-cli-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-1.0.0-1.git.2.94b76fc.el7.noarch
satellite-6.3.0-1.0.git.7.fb12bf2.el7sat.noarch

# rpm -qa | grep ansible
ansible1.9-1.9.6-2.el7.noarch
tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Import Ansible roles to Satellite
2. Associate Ansible roles to one or more clients in Satellite
3. Run Ansible role for a client by any of the following methods:
3.1 Go to Hosts -> Select (check) a Host -> Select Action -> Play Ansible Roles
3.2 Go to Hsots -> Click on a host -> Clicl `Ansible Roles` button

Actual results:
foreman task failed with an error "This action is not meant to be run"

Expected results:
No error and Ansible role runs on the client.

Additional info:
Comment 1 sthirugn@redhat.com 2016-10-19 18:00:31 UTC 
Created attachment 1212233 [details]
task failure
Comment 4 Daniel Lobato Garcia 2017-01-26 15:54:56 UTC 
Sthirugn,

Which version of foreman_ansible are you trying this with? There are many production users of it upstream and I just tried it before releasing and couldn't reproduce that error ""This action is not meant to be run"" in any way.

Mind to give a bit more details, or try with the latest version?
Comment 5 sthirugn@redhat.com 2017-02-06 14:16:10 UTC 
Hello Daniel,
I provided the foreman ansible version in the original bug description:

# rpm -qa | grep ansible
ansible1.9-1.9.6-2.el7.noarch
tfm-rubygem-foreman_ansible-1.2.1-1.fm1_13.el7.noarch
tfm-rubygem-foreman_ansible_core-0.0.1-2.fm1_13.el7.noarch

I can test this with latest 6.3 build once I am done with my current task.
Comment 6 Daniel Lobato Garcia 2017-02-13 15:52:55 UTC 
I'm not sure there are any 6.3 builds going to happen for a while - would you be able to test with upstream 1.4.3 for example?
Comment 8 Lukas Pramuk 2018-06-27 14:53:19 UTC 
VERIFIED.

@satellite-6.4.0-9.beta.el7sat.noarch
tfm-rubygem-foreman_ansible-2.2.0-1.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.1.0-1.el7sat.noarch
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
ansible-2.6.0-0.5.rc5.el7ae.noarch
ansiblerole-insights-client-1.5-1.el7sat.noarch

by manual reproducer described in comment#0 and used RedHatInsights.insights-client role.

Both step 3.1) and 3.2) works

>>> 100% success

@host: # rpm -q insights-client
insights-client-3.0.3-9.el7_5.noarch

>>> rpm is installed as the role was really played
Comment 9 Bryan Kearney 2018-10-16 19:12:14 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