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.
DescriptionJaroslav Krajicek
2020-11-03 11:30:03 UTC
Description of problem:
Need to execute commands on hosts using different SSH users based on the command in question.
Version-Release number of selected component (if applicable):
6.7
How reproducible:
Always
Steps to Reproduce:
1. Schedule a Remote Job for a host
2. Try to set remote_execution_ssh_user on the specific job invocation
Actual results:
Unable to set remote_execution_ssh_user per job on a host
Expected results:
Advanced fields containing 'SSH User' field
Additional info:
Setting SSH user per host or using an effective user is not satisfactory for a customer.
Hello, I was able to verify the functionality on 6.12 snap 1. The 'SSH user' field is present in advanced fields, it's values are applied correctly and it is repopulated on reruns.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:8506