Bug 1109104 - When gluster process monitoring service is started at boot time, "OK" or "FAILED" is not indicated
Summary: When gluster process monitoring service is started at boot time, "OK" or "FAI...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nagios-addons
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Timothy Asir
QA Contact: RHS-C QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 09:12 UTC by Shruti Sampat
Modified: 2018-08-14 11:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-30 11:11:58 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (23.90 KB, image/png)
2014-06-13 09:12 UTC, Shruti Sampat
no flags Details

Description Shruti Sampat 2014-06-13 09:12:28 UTC
Created attachment 908426 [details]
screenshot

Description of problem:
------------------------

When gluster process monitoring service is started at boot time, it is not indicated whether the service was started successfully or not. 

For other services and daemons, success or failure is indicated using the string "OK" or "FAILED". See screenshot.

Version-Release number of selected component (if applicable):
RHSS-3.0-20140612.n.0-RHS-x86_64-DVD1.iso

How reproducible:
Always

Steps to Reproduce:
1. Install RHSS 3.0 iso.
2. Observe boot messages at first boot.

Actual results:
Whether starting the gluster process monitoring service was successful or not is not indicated, unlike other services.

Expected results:
Whether starting the gluster process monitoring service was successful or not should be indicated by "OK" or "FAILED" being displayed.

Additional info:

Comment 2 Sahina Bose 2018-01-30 11:11:58 UTC
Thank you for your report. However, this bug is being closed as it's logged against gluster-nagios monitoring for which no further new development is being undertaken.


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