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:
Using a sudo password works in satellite 6.7.2 but doesn't work in 6.7.4
setting remote_execution_sudo_password and remote_execution_sudo_. I've noticed this is only the case for ansible rex jobs

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


How reproducible:
very

Steps to Reproduce:
1. Set up non-privileged user for remote execution 
2. set up password accessed sudo for remote execution user 
3. configure remote_execution_sudo_password and remote_execution_ssh_user so that remote execution should be able to work with a password to sudo to root.
4. Attempt to use remote execution to run ansible job or role that requires elevated privileges.

Actual results:
Password authentication fails

Expected results:
Password authentication succeeds 

Additional info:

If I recall correctly ansible_sudo_pass completely bypassed whatever effective use handling remote execution had. It was just a parameter that was processed directly by ansible itself. Ansible later introduced ansible_become_pass and eventually phased out ansible_sudo_pass[1]. Either you can set ansible_become_pass instead and keep bypassing REX or set remote_execution_effective_user_password and let satellite do its thing.

From where I'm standing it sounds like if there was a bug, it was fixed in the meantime. I'll go ahead and close this one, if you feel there is something to address here, feel free to reopen.

[1] - https://github.com/ansible/ansible/issues/64987