Bug 1897259

Summary: Still hit Bug #1870148 on oVirt 4.4.3.11
Product: [oVirt] ovirt-engine Reporter: jake.reynolds
Component: Setup.CoreAssignee: Ales Musil <amusil>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.3.11CC: bugs, dholler
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: Environment:
Last Closed: 2020-11-12 16:34:55 UTC Type: Bug
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 jake.reynolds 2020-11-12 16:12:13 UTC
Description of problem:
I have hit Bug 1870148, which is closed as being fixed in 4.4.3

Version-Release number of selected component (if applicable):
vdsm-4.40.26.3-1.el8.x86_64
oVirt engine - 4.4.3.11-1.el8


VDSM Log:
2020-11-12 16:02:55,750+0000 INFO  (jsonrpc/3) [api.network] START setupNetworks(networks={'ovirtmgmt': {'vlan': '110', 'bonding': 'bond0', 'ipv6autoconf': False, 'bridged': 'true', 'bootproto': 'dhcp', 'defaultRoute': True, 'dhcpv6': False, 'STP': 'no', 'mtu': 1500, 'switch': 'legacy'}}, bondings={'bond0': {'nics': ['eno2', 'eno1'], 'options': 'mode=4 miimon=100 xmit_hash_policy=2', 'switch': 'legacy'}}, options={'connectivityTimeout': 120, 'commitOnSuccess': True, 'connectivityCheck': 'true'})
2020-11-12 16:02:55,832+0000 ERROR (jsonrpc/3) [vds] Nics with multiple usages: {'eno1'} (API:1555)
Traceback (most recent call last):
  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)
vdsm.network.errors.ConfigNetworkError: (24, "Nics with multiple usages: {'eno1'}")
2020-11-12 16:02:55,833+0000 INFO  (jsonrpc/3) [api.network] FINISH setupNetworks return={'status': {'code': 24, 'message': "Nics with multiple usages: {'eno1'}"}}



How reproducible:
100%

Steps to Reproduce:
1. have a host with 4 NICS
2. Attach a vlan network to NIC3
3. Try to create bond from NIC3 and NIC4

Actual results:
Fail with interface already in use error

Expected results:
Should succeed

Additional info:

Comment 1 RHEL Program Management 2020-11-12 16:32:03 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 2 Sandro Bonazzola 2020-11-12 16:34:55 UTC
I see that the bug you are referring is marked as fixed in vdsm-4.40.28 while you are reporting this on vdsm-4.40.26.3-1.el8.x86_64.
Please upgrade your hosts to 4.4.3 as well.
In 4.4.3 we shipped vdsm 4.40.35.1

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

Comment 3 jake.reynolds 2020-11-13 09:22:54 UTC
I noticed the other comment in the bug (it wasn't totally clear that 'verified in vXXX' mean fixed in vXXX) after creating this.

Apologies, Katello had reported a successful sync but hadn't pulled in the latest packages - resyncing and upgrading to latest fixed the issue.