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:
When executing rex jobs as a root user, pull provider jobs by default execute in /, while ssh and ansible jobs use /root. This could bring surprises when porting scripts between providers.
Version-Release number of selected component (if applicable):
Satellie 6.12 sn 5
How reproducible:
Always
Steps to Reproduce:
1. run remote execution command pwd on remote host using pull provider and using ssh
Actual results:
ssh: /root
pp: /
Expected results:
consistency
No, not really. We didn't really pick either of those directories, for ssh it is just a side effect of how sshd processes incoming connections. In pull provider we don't configure the working directory at all so it just runs in whatever context systemd spawns it.
Correction to comment #2, yggdrasil actively reduces the environment for workers to only contain PATH and YGG_SOCKET_ADDR. We can still parse /etc/passwd to get the current user's working directory in the worker but that's more cumbersome than it should be.
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 (Satellite 6 Satellite Client 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/RHBA-2022:8507