Bug 807927 - rhn-satellite status output not uniform accross services
rhn-satellite status output not uniform accross services
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
541
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Jan Pazdziora
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2012-03-29 03:36 EDT by mertensb
Modified: 2015-05-29 16:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-05-29 16:12:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mertensb 2012-03-29 03:36:04 EDT
Description of problem:
rhn-satellite status output not uniform accross services


How reproducible:
Always

Steps to Reproduce:
$ sudo rhn-satellite status
  
Actual results:
$ sudo rhn-satellite status
router is stopped
sm is stopped
c2s is stopped
s2s is stopped
osa-dispatcher is stopped
tomcat6 is stopped                                         [  OK  ]
httpd is stopped
rhn-search is not running.
cobblerd is stopped
RHN Taskomatic is not running.


Expected results:
$ sudo rhn-satellite status
router is stopped                                    [  OK  ]
sm is stopped                                        [  OK  ]
c2s is stopped                                       [  OK  ]
s2s is stopped                                       [  OK  ]
osa-dispatcher is stopped                            [  OK  ]
tomcat6 is stopped                                   [  OK  ]
httpd is stopped                                     [  OK  ]
rhn-search is stopped                                [  OK  ]
cobblerd is stopped                                  [  OK  ]
RHN Taskomatic is stopped                            [  OK  ]


Additional info:

The words "is not running" in the status output is a bit confusing, it would be better to have a standard response from all services.

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