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.
DescriptionRudnei Bertol Jr.
2020-07-01 20:29:23 UTC
Description of problem:
When running an Ansible job using Satellite on a host that has a different sudo/ssh password to run the Ansible Job, it fails with the following error.
"""
fatal: [sat67a.example67a.local]: FAILED! => {"msg": "Missing sudo password"}
"""
Version-Release number of selected component (if applicable):
Satellite 6.7
How reproducible:
Run the Ansible Job template on a host as non-root user and became root setting the sudo password on the Job template invocation.
Steps to Reproduce:
1. Run the Ansible Job on a host that has a sudo password different for the password set on the settings, setting the password on the advanced option 'Sudo password' on the advanced option.
Actual results:
The sudo password set on the job invocation is invoked/used when the ansible-runner calls the playbook.
Expected results:
Would be good to use this option, specially when we are running the ansible job o a specific host that has a different sudo password that the entire environment.
Additional info:
Comment 2Rudnei Bertol Jr.
2020-07-01 20:42:38 UTC
Description of problem: When running an Ansible job using Satellite on a host that has a different sudo/ssh password to run the Ansible Job, it fails with the following error. """ fatal: [sat67a.example67a.local]: FAILED! => {"msg": "Missing sudo password"} """ Version-Release number of selected component (if applicable): Satellite 6.7 How reproducible: Run the Ansible Job template on a host as non-root user and became root setting the sudo password on the Job template invocation. Steps to Reproduce: 1. Run the Ansible Job on a host that has a sudo password different for the password set on the settings, setting the password on the advanced option 'Sudo password' on the advanced option. Actual results: The sudo password set on the job invocation is invoked/used when the ansible-runner calls the playbook. Expected results: Would be good to use this option, specially when we are running the ansible job o a specific host that has a different sudo password that the entire environment. Additional info: