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.
Description of problem:
Remote Execution with Sudo password in not working expected in Satellite 6.4
For reference, please refer the below documentation link:-
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/managing_hosts/chap-managing_hosts-running_remote_jobs_on_hosts#sect-Managing_Hosts-Configuring_Global_Settings
Version-Release number of selected component (if applicable):
satellite-common-6.4.0-15.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-2.0.1.11-1.el7sat.noarch
satellite-6.4.0-15.el7sat.noarch
satellite-installer-6.4.0.7-2.el7sat.noarch
satellite-cli-6.4.0-15.el7sat.noarch
rubygem-smart_proxy_remote_execution_ssh-0.2.0-3.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.5.6-4.el7sat.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.1.0-1.el7sat.noarch
How reproducible:
It is reproducible.
Steps to Reproduce:
1. On the client machine created a user and added it to the sudoers.
2. Added the below entry in the
echo "testuser ALL=ALL ALL" > /etc/sudoers.d/testuser
3. Added the value to the below parameter in the “Global Settings for Remote Execution”.
SSH User <>
Default SSH password <>
Effective User Method <>
Effective User <>
Actual results:
Got the below exception:-
1:[sudo] password for testuser:
2:Exit status: 1
Expected results:
The command should have executed, without prompting for password
Additional info:
I tried with root user and it worked as expected, the reason I am mentioning this as I did not exchange the ssh keys.
I created another BZ[1] to handle the encrypted settings. Meanwhile, a potentional workaround would be to unset the setting and create a global parameter (Configure > Global parameters) called remote_execution_sudo_password and set it as hidden. This would configure a password to be used globally for all hosts, but it wouldn't be shown in plaintext.
Because all of the concerns in this BZ were addressed or covered by another BZ, I'll go ahead and close this one. If you feel there is anything that remains unsolved, please feel free to reopen it.
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1654318