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 2013837 - Improve REX error reporting when uploading script
Summary: Improve REX error reporting when uploading script
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-13 20:54 UTC by Paul Dudley
Modified: 2024-12-20 21:23 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_remote_execution_ssh-0.5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:30:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6415951 0 None None None 2021-10-13 22:18:00 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:30:14 UTC

Description Paul Dudley 2021-10-13 20:54:13 UTC 
Component versions:
satellite-6.9.6.1-1.el7sat.noarch
tfm-rubygem-foreman_remote_execution-4.2.3.1-1.el7sat.noarch

Problem:
When initial file upload encounters messages from stderr REX task sends this message:
~~~
1: Error initializing command: RuntimeError - Unable to upload file to /var/tmp/foreman-ssh-cmd-77a1b01f-74c9-4a93-818e-c0023724c1a0/script on remote system: exit code: PIPE
2: Exit status: EXCEPTION
~~~

This was due to a profile.d script that could have been executed better, here:
~~~
[root@rhel8new ~]# cat /etc/profile.d/test.sh
echo "This is a test message" >&2
~~~

The stderr redirection causes SCP to see the message on login, and this seems to be the reason for the REX failure. For example:
~~~
[root@satellite ~]# scp testscript root.com:/var/tmp/testscript
This is a test message
testscript                                100%   10    11.8KB/s   00:00    
~~~

The root cause is resolved by executing the profile script better. This request is to ask that REX provide more transparency as to the cause of the issue in such a case.
Comment 1 Adam Ruzicka 2022-04-20 13:21:20 UTC 
This seems to be fixed by the move away from net/ssh in smart_proxy_remote_execution_ssh-0.5.0.
Comment 2 Peter Ondrejka 2022-05-02 11:15:31 UTC 
Verified on Satellite 6.11 snap 18. Having the above test script, the rex job does output the redirected message, which doesn't prevent it from executing successfully.
Comment 5 errata-xmlrpc 2022-07-05 14:30:00 UTC 
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 (Moderate: Satellite 6.11 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:5498
Note You need to log in before you can comment on or make changes to this bug.