RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1769963 - On errors, redhat-support-tool exits with zero exit code and writes to stdout
Summary: On errors, redhat-support-tool exits with zero exit code and writes to stdout
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: redhat-support-tool
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Vikas Rathee
QA Contact: Upgrades and Supportability
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-07 19:58 UTC by Joe Rafaniello
Modified: 2021-05-07 07:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-07 07:30:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Joe Rafaniello 2019-11-07 19:58:43 UTC
Description of problem:
We cannot write scripts to use redhat-support-tool because we cannot detect errors properly.  All failures with the tool appear to exit with a 0 exit code and write the error to standard output instead of standard error.

Version-Release number of selected component (if applicable):
redhat-support-tool-0.10.2-1.el8_0.noarch

How reproducible: Very
Steps to Reproduce:

# with invalid file, exits 0 on error
[root@ibm-p8-kvm-03-guest-02 ~]# redhat-support-tool addattachment /dev/null -c abcd
ERROR: /dev/null is not a valid file.
[root@ibm-p8-kvm-03-guest-02 ~]# echo $?
0 # I expect >=1

# with no configured userid, exits 0 on error
[root@ibm-p8-kvm-03-guest-02 ~]# redhat-support-tool kb abcd
Please enter your RHN user ID:
Unable to find a KB with an ID of abcd
[root@ibm-p8-kvm-03-guest-02 ~]# echo $?
0

# with user, no known kb article, exits 0
[root@ibm-p8-kvm-03-guest-02 ~]# redhat-support-tool kb abcd
Unable to fulfill request with support services API. Reason: Not Found
[root@ibm-p8-kvm-03-guest-02 ~]# echo $?
0

# all errors appear to be written to stdout, not stderr
[root@ibm-p8-kvm-03-guest-02 ~]# redhat-support-tool kb abcd 1> /dev/null
# nothing written to stderr...


Expected results:
All failed commands should exit with a non-zero exit code and write their errors to STDERR, not STDOUT.

Comment 1 Joe Rafaniello 2019-11-07 20:22:30 UTC
We ran into this problem after wrapping redhat-support-tool, as reported in bug #1767512

Comment 6 RHEL Program Management 2021-05-07 07:30:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.