Bug 2214194 - ssh user parameter when executing ansible playbook is not working as expected.
Summary: ssh user parameter when executing ansible playbook is not working as expected.
Keywords:
Status: CLOSED DUPLICATE of bug 2153727
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.13.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-12 09:24 UTC by Rohit Rajput
Modified: 2023-06-12 09:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-12 09:40:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rohit Rajput 2023-06-12 09:24:59 UTC
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.

Comment 1 Adam Ruzicka 2023-06-12 09:40:15 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.