Bug 1113103
| Summary: | Network Utilization [pnp4nagios] fails to load the graph | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Prasanth <pprakash> | ||||||
| Component: | rhsc | Assignee: | Ramesh N <rnachimu> | ||||||
| Status: | CLOSED CANTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | rhgs-3.0 | CC: | esammons, nlevinki, rhs-bugs, rhsc-qe-bugs, sankarshan, shtripat | ||||||
| Target Milestone: | --- | Keywords: | ZStream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| 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 15:11:03 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1087818 | ||||||||
| Attachments: |
|
||||||||
|
Description
Prasanth
2014-06-25 12:48:12 UTC
[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: | Created attachment 912089 [details]
screenshot which shows ALL Interfaces
For once, it shows ALL the interfaces in "Satatus Information". See attached!
sosreport please (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? 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 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. We should document it, so that, end-user does not get confused or feels "what's wrong with this?" 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. Yes. It worked that way. We are looking into sysstat code how to fix this issue. Moving it to 3.0.3 Thank you for your report. This bug is filed against a component for which no further new development is being undertaken |