Bug 1507869 - rhui-manager status has multiple issues
Summary: rhui-manager status has multiple issues
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Tools
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: RHUI Bug List
QA Contact: Vratislav Hutsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-31 10:58 UTC by Radek Bíba
Modified: 2021-09-09 12:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-26 13:50:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0347 0 normal SHIPPED_LIVE RHUI 3.0.2 bug fix update 2018-02-26 18:50:48 UTC

Description Radek Bíba 2017-10-31 10:58:30 UTC
Description of problem:
Issue #1: The command always prints the return code in its output. That doesn't seem necessary.

Issue #2: The usage message reads:

    --code - if specified, only a numeric code for the result will be displayed

However, here's what's displayed:

# rhui-manager status --code
Red Hat Enterprise Linux Atomic Host (Kickstart) from RHUI ............ Error

0

That's not only a numeric code. The only difference between using --code and not using it is in the absence of the entitlement CA certificate expiration date in the output.

Issue #3: As you can see above, the return code is 0 despite an error. (I can confirm that by running "echo $?", which also prints 0.) Shouldn't the return code be REPO_SYNC_ERROR, ie. 1? I can't take advantage of the return code in order to determine if everything is all right; I'd have to parse the output, which isn't very convenient.

Version-Release number of selected component (if applicable):
rh-rhui-tools-3.0.1-3.el7ui.noarch

Comment 6 errata-xmlrpc 2018-02-26 13:50:29 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, 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-2018:0347


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