Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1111549 - Trends are NOT working if the "Name" field in RHSC is NOT matching the 'Hostname' in Nagios
Trends are NOT working if the "Name" field in RHSC is NOT matching the 'Hostn...
Status: CLOSED CANTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
3.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Ramesh N
RHS-C QE
: ZStream
Depends On:
Blocks: 1087818 1111494
  Show dependency treegraph
 
Reported: 2014-06-20 06:17 EDT by Prasanth
Modified: 2018-08-14 07:15 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
In the Red Hat Storage Console, if the name provided in the "Name" field of the host in the "New Host" popup is different from the "Hostname" provided in Nagios, the utilization details for the hosts are not displayed in Trends tab.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-29 10:12:14 EST
Type: Bug
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 Prasanth 2014-06-20 06:17:24 EDT
Description of problem:

Trends are NOT working if the "Name" field in RHSC is NOT matching the 'Hostname' in Nagios

In RHSC, there is a field called 'Name' in Host popup. Currently, this field SHOULD match the host name in Nagios for the Trends to work in RHSC. IMO, this is not the right way to map. Since the "Name" field can have any unique name as per the admin's choice, mapping this field with Nagios for the pnp4nagios charts to work is NOT a good idea. Since there is a separate field below that called "Address" in which the IP address, or resolvable hostname of the host is expected as the input, we can't expect the "Name" field also to have the same Hostname value.

The Admin should have the flexibility to give any value in the "Name" field as per his/her choice for the servers in a cluster for various reasons. Just for making RHSC Trends to work with pnp4nagios, we can't mandate them to enter Hostname in the "Name" field as well. 

When we execute the auto discovery script (/usr/lib64/nagios/plugins/gluster/discovery.py) from the RHSC + Nagios Server, the conf files are generated with the resolvable hostname of the servers, which is fine. The same resolvable Hostname or it's corresponding address will definitely be present in the "Address" field of ANY host added to a cluster in RHSC. So we should have ideally mapped it to the same "Address" field instead of "Name" field. 

Version-Release number of selected component (if applicable):
rhsc-3.0.0-0.11.el6_5.noarch


How reproducible: 100%


Steps to Reproduce:
1. In RHSC, click on "New Host" and enter ANY name of your choice in "Name" field and enter the Hostname or IP of the server in "Address" field.
2. Add 2 servers in the same way
3. Try to get the Trends for the Hosts

Actual results: Trends are NOT working if the "Name" field is NOT matching the Hostname of the server which is present in the NAgios conf files.


Expected results: Trends should work irrespective of the value in the "Name" field.


Additional info:
Comment 1 Shalaka 2014-06-26 02:04:08 EDT
Review and signoff edited doc text.
Comment 2 Ramesh N 2014-06-26 06:35:13 EDT
Doc text looks good to me.
Comment 4 Dusmant 2014-09-25 03:36:11 EDT
We should find a proper fix for this. RHSC should configures Nagios server with the host names using which it's managing the nodes in the cluster. OR Auto discovery should be able to access the data from RHSC. 

Ramesh is working on this and it might take some time to choose the correct approach. So, pushing it out to 3.0.3
Comment 5 Sahina Bose 2018-01-29 10:12:14 EST
Thank you for your report. This bug is filed against a component 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.