Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Critical: Satellite 6.16.0 release), 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-2024:8906

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.

I can verify that configuring the "SSH user" and the "Effective user" within the Advanced Fields of the Job Template functions correctly. However, the provided values for the "SSH password" and the "Effective user password" in the Advanced Fields of the Job Template do not work as expected.

Please note that with the recent updates, if the `remote_execution_ssh_user` is defined as a host parameter, it will only be utilized if the "SSH user" is not specified in the Advanced Fields of the Job Template.

Verified.

Tested on Satellite Stream Snap 56.0
Version: rubygem-foreman_ansible-14.0.0-1.el9sat.noarch

Steps:
1. Ensure ssh_user and effective_user to root from the "Administer => Settings", "Remote Execution" tab
2. Register a host, and on the Hosts page, select a host, and run "Schedule Remote Job"
3. Select job category "Ansible Playbook" and Job Template "Ansible Roles - Ansible Default"
4. From the Advanced Fields, select "SSH User" to a non-root user (a user that exists on the client, and the foreman-proxy public key has been shared with)
5. verify /var/log/secure on the client to check ssh connection using which user

OR
3. Use "Ansible Playbook - Ansible Run Playbook" job with below playbook to validate ansible_user,
—

• name: Verify Ansible user
  hosts: all
  gather_facts: false
  tasks:
• name: Display Ansible user
  debug:
  msg: "Ansible is running as user {{ ansible_user }}"

4. From the Advanced Fields, Select "SSH User" to a non-root user, check stdout for executed job and verify /var/log/secure on the client.

Observation:
The "SSH user" selected in the Advanced Fields of the Job Template is used correctly

customer in 03757734 also reported that the override value for the ssh_user password (password field in the "Advanced fields" section) will not work when he uses "remote_execution_ssh_user" parameter on the host. I confirmed this also with my satellite.

This seem to leave the only workable solution for Ansible REX with the override value for non-ssh user is to:

1) "remote_execution_ssh_user" parameter on the host
2) deploy the ssh key to the non-root user (passwdless ssh)

Unless there is a different workaround like "remote_execution_ssh_user_password" parameter on the host which I tested and did not work.