Bug 1870148
| Summary: | Cannot bond a NIC with vlan tagged network attachment | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Michael Burman <mburman> |
| Component: | Core | Assignee: | Ales Musil <amusil> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Guy <gafik> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.40.19 | CC: | bugs, dholler, jake.reynolds, mavital, mperina |
| Target Milestone: | ovirt-4.4.3 | Flags: | mperina:
ovirt-4.4?
mavital: testing_plan_complete- dholler: planning_ack? dholler: devel_ack+ mburman: testing_ack+ |
| Target Release: | 4.40.28 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | vdsm-4.40.28 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-11 06:39:37 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: | |||
Verified in version v4.40.28 This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. *** Bug 1897259 has been marked as a duplicate of this bug. *** Due to QE capacity, we are not going to cover this issue in our automation |
Description of problem: Cannot bond a NIC with vlan tagged network attachment When trying to create a bond from a slave NIC that has a vlan tagged network attachment on top of him, we fail with: engine: Error while executing action HostSetupNetworks: Interface already in use Close vdsm: 2020-08-19 15:49:06,114+0300 ERROR (jsonrpc/0) [vds] Nics with multiple usages: {'ens4f2'} (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: {'ens4f2'}") 2020-08-19 15:49:06,116+0300 INFO (jsonrpc/0) [api.network] FINISH setupNetworks return={'status': {'code': 24, 'message': "Nics with multiple usages: {'ens4f2'}"}} Version-Release number of selected component (if applicable): vdsm-4.40.25-1.el8ev.x86_64 nmstate-0.3.4-10.el8.noarch 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: Similar scenario as BZ 1793983 but with vlan