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.

Description of problem:

On host list page, select host and do Select Action > Play ansible role. Job immediately starts without letting you to select the job category, template, query, etc. You have to hit "rerun" on the job page to get to the d

Version-Release number of selected component (if applicable):
Satellite 6.5 snap 2 (will check 6.4 too)

How reproducible:
Always


Actual results:
Some default role is run

Expected results:
Possibility to select parameters of playbook run.

Additional info:
BTW, I'm not sure why the "Play ansible role" option is in the action is there when "Schedule remote job" does the same thing

Happens also in 6.4

I think the difference is that "Schedule remote job" takes you to the new job invocation form where you can specify what to run and "Play ansible roles" takes the list of roles assigned to the host and runs them immediately.

From upstream docs[1]:

> Alternatively, you can run the playbook for all Ansible roles applicable to hosts in a host group by clicking on the Play roles button on the Host groups page.

I'd say this works as expected.

[1] - https://theforeman.org/plugins/foreman_ansible/2.x/index.html#4.3RunningAnsibleRoles

Peter, should we close this based upon comment 5?

I agree this is intentional behaviour. Feel free to re-open in disagreement.

Ok, I understand now why the option exists, though it is hard to figure out what is happening without knowing that particular line in docs, even after running the play. An easy way to improve would be making the option name more informative, something like "Play all Ansible roles from hostgroup". Therefore filing this humble rfe here:  https://bugzilla.redhat.com/show_bug.cgi?id=1653217