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.
Bug 2051999 - Changing to effective_user does not work when async_ssh is true and the user method requires a password
Summary: Changing to effective_user does not work when async_ssh is true and the user ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-08 13:53 UTC by Adam Ruzicka
Modified: 2024-01-09 19:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-04 21:29:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18397 0 None None None 2023-06-14 12:06:54 UTC

Internal Links: 2048560

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.
Note You need to log in before you can comment on or make changes to this bug.