Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1858726

Summary: [Docs] Failed to assign network to Infiniband Bond
Product: Red Hat Enterprise Virtualization Manager Reporter: Dominik Holler <dholler>
Component: vdsmAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: amusil, arusakov, bugs, dholler, lsurette, lsvaty, mperina, srevivo, ycui
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1856279 Environment:
Last Closed: 2020-07-21 08:57:14 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:

Description Dominik Holler 2020-07-20 08:35:49 UTC
We should document that Infiniband cannot be configured on RHV-4.4 hosts yet.
The workaround is to use RHV-4.3 hosts on RHVM-4.4 for hosts with Infiniband.


+++ This bug was initially created as a clone of Bug #1856279 +++

Description of problem:

Version-Release number of selected component (if applicable):
oVirt 4.4.1.8-1.el8

How reproducible:

Steps to Reproduce:
1. Create Infiniband Bond 
2. Create new network with MTU 65520 (uncheck VM Network)
3. Assign created network to IB bond (Go to Hosts --> Netwrok Interface. Drag to IB Bond, press OK)

Actual results:
Error -  "Error while executing action HostSetupNetworks: Unexpected exception"

Expected results:
New network assigned to IB Bond. 

Additional info:

VDSM log 
2020-07-11 15:33:39,147+0300 INFO (jsonrpc/1) [api.network] START
setupNetworks(networks={'IB': {'netmask': '255.255.255.0',
'bonding': 'bond1', 'ipv6autoconf': False, 'bridged':
'false', 'ipaddr': '172.17.***.***', 'dhcpv6': False,
'mtu': 65520, 'switch': 'legacy'}}, bondings={},
options={'connectivityTimeout': 120, 'commitOnSuccess': True,
'connectivityCheck': 'true'}) from=::ffff:172.16.***.***,33614,
flow_id=fe589281-3171-41b4-b7aa-e28a4bbebe55 (api:48)
2020-07-11 15:33:40,088+0300 INFO (jsonrpc/1) [api.network] FINISH setupNetworks
error=MAC address cannot be specified in bond interface along with specified bond options
from=::ffff:172.16.***.***,33614, flow_id=fe589281-3171-41b4-b7aa-e28a4bbebe55 (api:52)
2020-07-11 15:33:40,088+0300 ERROR (jsonrpc/1) [jsonrpc.JsonRpcServer] Internal server
error (__init__:350)
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/yajsonrpc/__init__.py", line 345, in
_handle_request
res = method(**params)
File "/usr/lib/python3.6/site-packages/vdsm/rpc/Bridge.py", line 198, in
_dynamicMethod
result = fn(*methodArgs)
File "<decorator-gen-480>", line 2, in setupNetworks
File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in
method
ret = func(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/vdsm/API.py", line 1548, in
setupNetworks
supervdsm.getProxy().setupNetworks(networks, bondings, options)
File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in
__call__
return callMethod()
File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in
<lambda>
**kwargs)
File "<string>", line 2, in setupNetworks
File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in
_callmethod
raise convert_to_error(kind, result)
libnmstate.error.NmstateValueError: MAC address cannot be specified in bond interface
along with specified bond options

--- Additional comment from RHEL Program Management on 2020-07-14 08:35:18 UTC ---

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 1 Dominik Holler 2020-07-21 08:57:14 UTC

*** This bug has been marked as a duplicate of bug 1858731 ***