Bug 1496677
| Summary: | [downstream clone - 4.1.7] NPE when get LLDP info from host interface via REST | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | vdsm | Assignee: | Dominik Holler <dholler> |
| Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.1.6 | CC: | bazulay, danken, edwardh, lsurette, mgoldboi, srevivo, trichard, ycui, ykaul |
| Target Milestone: | ovirt-4.1.7 | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, VDSM expected the optional object identifier OID field in Link Layer Discovery Protocol (LLDP). If this was absent, parsing of LLDP failed. Now, VDSM no longer expects the object identifier OID field in LLDP. LLDP info from the host is presented via the REST API without an object identifier OID.
|
Story Points: | --- |
| Clone Of: | 1494921 | Environment: | |
| Last Closed: | 2017-11-07 17:29:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1494921 | ||
| Bug Blocks: | |||
|
Description
rhev-integ
2017-09-28 06:10:16 UTC
Created attachment 1330100 [details]
vds, supervdsm and engine logs
(Originally by Meni Yakove)
8.5.9.7 object identifier (OID) string length The object identifier string length field shall contain the length, in octets, of the OID. A value of zero in this field indicates that the OID field is not provided. Seems like the OID field is optional. (Originally by edwardh) nope, the code is not in today's vdsm-4.19.33 Verified on - vdsm-4.19.35-1.el7ev.x86_64 and 4.1.7.4-0.1.el7 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:3139 |