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 1492585 - [RFE] Add --brief and --quiet parameters to katello-service status
Summary: [RFE] Add --brief and --quiet parameters to katello-service status
Keywords:
Status: CLOSED DUPLICATE of bug 1366691
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Usability
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-18 09:03 UTC by Luc de Louw
Modified: 2017-09-20 19:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-20 19:20:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Luc de Louw 2017-09-18 09:03:37 UTC
Description of problem:

When running "katello-service status", one gets flooded by information in the output, usually one would just like to know if a service is in status running or failed w/o the additional output.

It would be great to add a parameter --brief which omits the additional output

A parameter --quiet which returns nothing than an exit code (0=all fine, non-0=something is wrong would be handy for simple monitoring purposes.

Version-Release number of selected component (if applicable):
katello-service-3.0.0-20

How reproducible:
Always

Steps to Reproduce:
1. Run katello-service status
2. Search for "failed" or similar in the output
3. Getting confused and miss the important information

Actual results:


Expected results:


Additional info:

Comment 2 Brad Buckingham 2017-09-20 19:20:04 UTC

*** This bug has been marked as a duplicate of bug 1366691 ***


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