Bug 1514575
| Summary: | Node agent unable to collect network details | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nishanth Thomas <nthomas> |
| Component: | web-admin-tendrl-node-agent | Assignee: | gowtham <gshanmug> |
| Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | mkudlej, nthomas, rhinduja, rhs-bugs, rkanade, sankarshan, ssaha |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tendrl-node-agent-1.5.4-3.el7rhgs.noarch | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-18 04:37:04 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: | |||
|
Description
Nishanth Thomas
2017-11-17 19:25:32 UTC
Could you please describe reproducer for this bug? @MartinK, To reproduce this issue, you need to use Ovirt/RHEVM and create VM's (storage nodes and Tendrl server). Install tendrl-node-agent on any such VM and check logs, although you wont see the issue with latest Tendrl builds. The issue specifically is about "vdsdummy" which is a bridge that VDSM daemon creates. When such bridge is seen, the hwinfo/ethtool used by tendrl-node-agent returns a warning/traceback along with list of networks. We have simply sent a patch which ignores such warnings and process the networks as is. https://access.redhat.com/solutions/962933 https://github.com/Tendrl/node-agent/blob/master/tendrl/node_agent/node_sync/network_sync.py#L104 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3478 |