Description of problem: oVirt should provide Link Layer Discovery Protocol (LLDP) Support. oVirt hosts should gather information from their networking interfaces and let oVirt Engine provide this information on REST-API, like described in https://github.com/oVirt/ovirt-site/pull/1027 Actual results: No LLDP information in oVirt REST-API available Expected results: LLDP information in oVirt REST-API available
REST is not merged for 4.1 <host_nichref="/ovirt-engine/api/hosts/9d1d577b-a482-42ef-82c7-7d74169958fa/nics/eae47b64-a78a-4476-a74d-8f29b9ec7d62"id="eae47b64-a78a-4476-a74d-8f29b9ec7d62"> <actions/> <name>enp2s0f0</name> <linkhref="/ovirt-engine/api/hosts/9d1d577b-a482-42ef-82c7-7d74169958fa/nics/eae47b64-a78a-4476-a74d-8f29b9ec7d62/networklabels"rel="networklabels"/> <linkhref="/ovirt-engine/api/hosts/9d1d577b-a482-42ef-82c7-7d74169958fa/nics/eae47b64-a78a-4476-a74d-8f29b9ec7d62/networkattachments"rel="networkattachments"/> <linkhref="/ovirt-engine/api/hosts/9d1d577b-a482-42ef-82c7-7d74169958fa/nics/eae47b64-a78a-4476-a74d-8f29b9ec7d62/statistics"rel="statistics"/> <boot_protocol>none</boot_protocol> <bridged>false</bridged> <ip> <address/> <netmask/> <version>v4</version> </ip> <ipv6_boot_protocol>none</ipv6_boot_protocol> <mac> <address>00:e0:ed:33:c0:96</address> </mac> <mtu>1500</mtu> <speed>1000000000</speed> <status>up</status> <hosthref="/ovirt-engine/api/hosts/9d1d577b-a482-42ef-82c7-7d74169958fa"id="9d1d577b-a482-42ef-82c7-7d74169958fa"/> </host_nic> No linklayerdiscoveryprotocolelements Also the feature page says that in the REST the name is linklayerdiscoveryprotocolinformationelements but in REST it's linklayerdiscoveryprotocolelements
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.
Hi Lev, ON_QA on which version?
Michael: 4.1.6.1
We decided to verify this RFE with the known issue described in BZ 1487930(see comment#18). "Cisco is sending LLDP packets encapsulated in VLAN1, which is probably the native tag on the port. This is a known problem of Cisco devices." - If using a cisco switch user must create a vlan tagged network with vlan tag 1 and only then lldp will be work for the port. - This should be added in the know issues of the release. Verified on - 4.1.6.2-0.1.el7 Dominik please make sure this will documented as part of the known issues in the release note.