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:
Created attachment 1212233 [details] task failure
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?
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.
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?
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
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