Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1143044

Summary: Gluster: Nagios plugin does not show trends
Product: [oVirt] ovirt-engine Reporter: Ravi Nori <rnori>
Component: Frontend.WebAdminAssignee: anmol babu <anbabu>
Status: CLOSED WORKSFORME QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: anbabu, bugs, gklein, lsurette, mgoldboi, rbalakri, rnori, sabose, sanandpa, sankarshan, srevivo, ykaul
Target Milestone: ovirt-4.0.4Flags: ykaul: ovirt-4.0.z?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-26 08:08:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Trends tab
none
clusters graph
none
Hosts' graph
none
Host1 graph
none
vol1 graph none

Description Ravi Nori 2014-09-17 19:40:01 UTC
Created attachment 938619 [details]
Trends tab

Description of problem: The nagios trends plugin does not show the images for the trends


Version-Release number of selected component (if applicable):


How reproducible: 3.5


Steps to Reproduce:
1. Install nagios server and configure following instructions on http://www.ovirt.org/Features/Nagios_Integration
2. Install trends plugin in webadmin and configure to connect to nagios server
as indicated on the feature page above
3. browse to trends tab

Actual results: No trends are shown


Expected results: The trends are displayed

Additional info:

A framework error is displayed when I right click on the broken image and select view image with the following error message

Please check the documentation for information about the following error.

XML file "/var/lib/pnp4nagios/C_34/Cluster_Utilization.xml" not found. <a href="http://docs.pnp4nagios.org/faq/6">Read FAQ online</a>
file [line]:

application/models/data.php [312]:

Comment 1 Sahina Bose 2014-09-18 05:46:24 UTC
Can you confirm that the cluster-name C_34 is the same name given to the cluster in Nagios as well (it should be seen as a host in Nagios)?

This issue happens when the names do not match.

Comment 2 Ravi Nori 2014-09-18 14:02:23 UTC
I had named the cluster 'cluster1'. I started fresh and did the whole thing again calling the cluster 'cluster1'. Still have the same problem error below. I checked the directory /var/lib/pnp4nagios/cluster1/ on the server and it does exist. 

From the error message below looks like the wrong xml file is being looked up, it should be 

/var/lib/pnp4nagios/cluster1/Cluster%5FUtilization.xml 
but it is 
/var/lib/pnp4nagios/cluster1/Cluster%20Utilization.xml 


Contents of directory
=====================
[root@localhost rnori]# ls /var/lib/pnp4nagios/cluster1/
Cluster_Utilization.rrd  Volume_Utilization_-_gv0.rrd
Cluster_Utilization.xml  Volume_Utilization_-_gv0.xml


Error
======

Please check the documentation for information about the following error.

XML file "/var/lib/pnp4nagios/cluster1/Cluster%20Utilization.xml" not found. <a href="http://docs.pnp4nagios.org/faq/6">Read FAQ online</a>
file [line]:

application/models/data.php [312]:

back

Comment 3 Sandro Bonazzola 2015-01-21 16:08:37 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 4 Red Hat Bugzilla Rules Engine 2015-10-19 10:52:18 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Sandro Bonazzola 2015-10-26 12:46:06 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 6 Sandro Bonazzola 2015-11-05 08:22:07 UTC
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high

Comment 7 Red Hat Bugzilla Rules Engine 2015-11-16 14:07:38 UTC
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset.
Please set the correct milestone or add the flag.

Comment 8 Yaniv Lavi 2015-12-10 08:41:21 UTC
Can you have a look?

Comment 9 Red Hat Bugzilla Rules Engine 2015-12-11 02:16:08 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.

Comment 10 Sahina Bose 2016-04-12 13:48:43 UTC
Shwetha, can you check the How to steps at http://www.ovirt.org/develop/release-management/features/infra/nagios-integration/ and see if you reproduce this error?

Otherwise we can close this bug.

Comment 11 Sandro Bonazzola 2016-05-02 10:03:48 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 12 Yaniv Lavi 2016-05-23 13:18:34 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 13 Yaniv Lavi 2016-05-23 13:22:38 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 14 Sweta Anandpara 2016-07-26 07:31:54 UTC
Tried the same on 3.7.9-10 with console + nagios setup for 3 node cluster. Trends tab does show all the graphs related to cluster, volume and all hosts. 

Having said that, there are a couple of prerequisites:

* Nagios page (https://<mgmt_ip>/nagios) should correctly display 'green' status with respect to cluster, hosts, volume and all services. IF the graph is not visible in the nagios web UI (for whatever reason), then the graphs will not be seen in the Trends tab as well.

* Hosts have to be the same name, when configured in console, as displayed by 'hostname' command
  Cluster name that is used while configuring console has to be the same one that is used while configuring nagios.

Once the above conditions are met, all the expected graphs are seen in Trends tab.

Please see attachments for more details. This BZ can be moved to its final state.

Comment 15 Sweta Anandpara 2016-07-26 07:34:37 UTC
Created attachment 1184082 [details]
clusters graph

Comment 16 Sweta Anandpara 2016-07-26 07:36:25 UTC
Created attachment 1184083 [details]
Hosts' graph

Comment 17 Sweta Anandpara 2016-07-26 07:37:31 UTC
Created attachment 1184084 [details]
Host1 graph

Comment 18 Sweta Anandpara 2016-07-26 07:38:10 UTC
Created attachment 1184085 [details]
vol1 graph

Comment 19 Sahina Bose 2016-07-26 08:08:35 UTC
Thanks Sweta!!
Based on Comment 14, closing this.