Bug 2081359 - IPoIB interfaces not reported by supervdsm network_caps
Summary: IPoIB interfaces not reported by supervdsm network_caps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.1
: ---
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-03 14:09 UTC by Raul Aldaz
Modified: 2022-07-14 12:41 UTC (History)
11 users (show)

Fixed In Version: vdsm-4.50.1.1-1.el8ev.x86_64
Doc Type: Bug Fix
Doc Text:
Infiniband interfaces are now reported by VDSM.
Clone Of:
Environment:
Last Closed: 2022-07-14 12:41:13 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt vdsm pull 184 0 None open net: Show IB interface in capabilities 2022-05-18 10:48:40 UTC
Red Hat Issue Tracker RHV-45922 0 None None None 2022-05-03 14:22:21 UTC
Red Hat Product Errata RHBA-2022:5583 0 None None None 2022-07-14 12:41:29 UTC

Description Raul Aldaz 2022-05-03 14:09:52 UTC
Description of problem:

IPoIB are configured and working in Host, but they are not reported by supervdsm network_caps()


Version-Release number of selected component (if applicable):

vdsm-4.40.100.2-1.el8ev.x86_64

How reproducible:

Not possible

Steps to Reproduce:

IPoIB example configuration used in related case:

nmcli connection add type infiniband con-name ib0 ifname ib0 transport-mode datagram mtu 2044
nmcli connection modify ib0 ipv4.addresses '1.1.0.112/16'
nmcli connection modify ib0 ipv4.method manual
nmcli connection modify ib0 ipv4.never-default true
nmcli connection modify ib0 ipv6.method disabled
nmcli connection up ib0

Then, examine network_caps entries on supervdsm.log file of Host.


Actual results:

network_caps() of supervdsm does not report interface.

Comment 9 Michal Skrivanek 2022-05-18 05:53:34 UTC
how is this one different from bug 1856279 / https://github.com/nmstate/nmstate/pull/1345 ?

Comment 10 Ales Musil 2022-05-18 05:59:50 UTC
(In reply to Michal Skrivanek from comment #9)
> how is this one different from bug 1856279 /
> https://github.com/nmstate/nmstate/pull/1345 ?

This is about reporting the device in capabilities, that one was about assigning it a network, which
should work only with non-VM networks.

Comment 18 Michael Burman 2022-06-08 12:09:10 UTC
Verified on - vdsm-4.50.1.1-1.el8ev.x86_64 and rhvm-4.5.1-0.62.el8ev.noarch

Comment 23 errata-xmlrpc 2022-07-14 12:41:13 UTC
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 (RHV RHEL Host (ovirt-host) [ovirt-4.5.1] update), 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/RHBA-2022:5583


Note You need to log in before you can comment on or make changes to this bug.