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 running a REX job via SSH from the Satellite to an RHEL8 host with tlog [1] enabled, it fails with the following error.

~~~
Error initializing command: RuntimeError - Unable to upload file to ... on remote system: exit code: PIPE
Exit status: EXCEPTION
~~~

[1] - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/recording_sessions/index

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

Satellite 6.8

How reproducible:

Try to run any REX job via SSH into an RHEL 8 host with tlog.

A reproducer environment will be available on a private comment.

Steps to Reproduce:
1. 
2.
3.

Actual results:

The REX fails with the following message.

~~~
   1:
Error initializing command: RuntimeError - Unable to upload file to /var/tmp/foreman-ssh-cmd-1a5fd374-5dda-4e8b-b3da-2119ca2e7b69/script on remote system: exit code: PIPE
   2:
Exit status: EXCEPTION
~~~

Expected results:

Be able to execute a REX job via ssh on an RHEL 8 host

Additional info:

I finally got around to setting up a new enough rhel with tlog enabled. Good news is the changes we did to smart_proxy_remote_execution_ssh which are going to land in Satellite 7.0 seem to fix this as well. Bad news is the changes are too large to backport so this will be a 7.0+ only thing.

Verified on Satellite 6.12 sn3, ssh job ran successfully against a host that records a tlog session and has with customizations in /etc/profile.d

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