Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1113103 - Network Utilization [pnp4nagios] fails to load the graph
Network Utilization [pnp4nagios] fails to load the graph
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
  Show dependency treegraph
 
Reported: 2014-06-25 08:48 EDT by Prasanth
Modified: 2018-08-14 07:16 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: Sometimes sadf output is corrupted on first day of installation of VM and gets correct after midnight for the next day output Consequence: The network utilization graph shows an error saying RRD data does not exist Workaround (if any): After midnight for the next day, the sadf output file gets corrected automatically and graph works fine. Result: NA
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-29 10:11:03 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)
screenshot of error (28.03 KB, image/png)
2014-06-25 08:48 EDT, Prasanth
no flags Details
screenshot which shows ALL Interfaces (240.28 KB, image/png)
2014-06-25 08:58 EDT, Prasanth
no flags Details

  None (edit)
Description Prasanth 2014-06-25 08:48:12 EDT
Created attachment 912086 [details]
screenshot of error

Description of problem:

Network Utilization [pnp4nagios] fails to load the graph

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 3.0.0-0.12.el6rhs

How reproducible: 100%


Steps to Reproduce:
1. Install and setup the latest RHSC3.0 build from Errata or from the local repo: http://rhsqe-repo.lab.eng.blr.redhat.com/rhsc3.0-console-latest/
2. Install and setup 2 RHS3.0 nodes
3. From RHSC, create a 3.4 cluster and add the above 2 RHS nodes.
4. Now, execute the following auto-config script from the engine:
 # /usr/lib64/nagios/plugins/gluster/discovery.py -c <cluster-name> -H <ip-address>
5. Take the Nagios portal and click on the Network Utilization graph icon

Actual results:  Network Utilization graph fails with the following error:

---------
Please check the documentation for information about the following error.

XML file "/var/lib/pnp4nagios/dhcp43-15.lab.eng.blr.redhat.com/Network_Utilization.xml" not found. Read FAQ online
file [line]:

application/models/data.php [312]:
---------

Expected results: Network Utilization graph should load sucessfully


Additional info: See attached screenshot
Comment 1 Prasanth 2014-06-25 08:54:54 EDT
[root@dhcp42-178 nagios]# /usr/lib64/nagios/plugins/gluster/network.py -e lo -e ';vdsmdummy;' -t 2
ERROR:root:unable to get ipaddr/flags for eth0: [Errno 99] Cannot assign requested address
OK:  |
Comment 2 Prasanth 2014-06-25 08:58:38 EDT
Created attachment 912089 [details]
screenshot which shows ALL Interfaces

For once, it shows ALL the interfaces in "Satatus Information". See attached!
Comment 3 Bala.FA 2014-06-25 12:43:52 EDT
sosreport please
Comment 4 Prasanth 2014-06-27 11:09:58 EDT
(In reply to Bala.FA from comment #3)
> sosreport please

I already gave access to the test setup for further debugging. Hope you gathered all the required details during that time?
Comment 5 Bala.FA 2014-06-27 22:26:17 EDT
We found the issue with sysstat and it corrected itself next day ie ovirtmgmt bridge is found in sadf output.

Not sure why it happened.  Will be investigated and fixed accordingly
Comment 6 Shubhendu Tripathi 2014-07-01 02:55:24 EDT
Similar issues with sadf output is seen for other physical services like Memory, Swap and CPU Utilization as well. The output is corrupted on first day but automatically gets corrected for the next day after midnight and services start working properly and graphs are displayed correctly.
Comment 7 Dusmant 2014-07-03 01:29:08 EDT
We should document it, so that, end-user does not get confused or feels "what's wrong with this?"
Comment 9 Shubhendu Tripathi 2014-07-10 04:22:57 EDT
As Bala confirmed there is an issue with sadf and at the time of day change (midnight) the sadf does not return any value.

Bala, please confirm the same.
Comment 10 Bala.FA 2014-07-10 05:25:02 EDT
Yes.  It worked that way.  We are looking into sysstat code how to fix this issue.
Comment 12 Dusmant 2014-09-25 03:15:44 EDT
Moving it to 3.0.3
Comment 14 Sahina Bose 2018-01-29 10:11:03 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.