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:
Unable to execute remote execution job for ansible-playbook if the ssh user value is set during the job and removed the user value from Administer -> Settings -> Remote execution -> ssh user
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.13.
How reproducible:
Always
Steps to Reproduce:
1. Remove the ssh user value from Administer -> Settings -> Remote execution tab.
2. Select the host to schedule remote exection job.
3. Select Job Catagory as Ansible Playbook and Job template as Ansible Roles - Ansible Default.
4. Under Advanced fields put value of ssh user for example: rexuser and run the job.
Actual results:
- The job fails with below error:
~~~
fatal: [satellite.example.com]: UNREACHABLE! => {"changed": false, "msg": "Invalid/incorrect password: \n\nPermission denied, please try again.", "unreachable": true}
~~~
Expected results:
- The job should execute successfully.
Additional info:
- If we set the ssh user value in Administer -> Settings -> Remote execution -> SSH User, for example, rexuser then the task is completed successfully.
This feels like a duplicate of BZ2153727 . If you feel the two BZs describe different issues, feel free to reopen.
*** This bug has been marked as a duplicate of bug 2153727 ***
Description of problem: Unable to execute remote execution job for ansible-playbook if the ssh user value is set during the job and removed the user value from Administer -> Settings -> Remote execution -> ssh user Version-Release number of selected component (if applicable): Red Hat Satellite 6.13. How reproducible: Always Steps to Reproduce: 1. Remove the ssh user value from Administer -> Settings -> Remote execution tab. 2. Select the host to schedule remote exection job. 3. Select Job Catagory as Ansible Playbook and Job template as Ansible Roles - Ansible Default. 4. Under Advanced fields put value of ssh user for example: rexuser and run the job. Actual results: - The job fails with below error: ~~~ fatal: [satellite.example.com]: UNREACHABLE! => {"changed": false, "msg": "Invalid/incorrect password: \n\nPermission denied, please try again.", "unreachable": true} ~~~ Expected results: - The job should execute successfully. Additional info: - If we set the ssh user value in Administer -> Settings -> Remote execution -> SSH User, for example, rexuser then the task is completed successfully.