Bug 2051999

Summary:	Changing to effective_user does not work when async_ssh is true and the user method requires a password
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Remote Execution	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	aruzicka, jpasqual, jsenkyri, lstejska
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 02:21:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Ruzicka 2022-02-08 13:53:26 UTC

Description of problem:
This is a spiritual successor of https://bugzilla.redhat.com/show_bug.cgi?id=2048560 with emphasis on using a password

If I'm reading things right this never worked, in contrast to BZ #204860 which worked in the past.

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

How reproducible:
always


Steps to Reproduce:
1. Set up a host to allow ssh connection as an uprivileged user
2. Set up the host to allow the user to become root using sudo with password
3. Run a job against that host

Actual results:
Until BZ #2048560 is fixed, the job will run as connection user.
After BZ #2048560 is fixed, I assume the job would fail, but it might just hang indefinitely.

Expected results:
The job runs as effective user


Additional info:

Comment 5 Brad Buckingham 2023-09-01 21:10:52 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Brad Buckingham 2023-10-04 21:29:50 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 9 Brad Buckingham 2023-12-01 18:41:30 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 11 Brad Buckingham 2024-01-09 19:59:00 UTC

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Comment 12 Eric Helms 2024-06-06 02:21:50 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.