Description of problem: error: unsupported configuration: an interface connecting to network 'ovs-network' is requesting a vlan tag, but that is not supported for this type of network Version-Release number of selected component (if applicable): v5.5.0 How reproducible: Steps to Reproduce: 1.create ovs-network with some portgroups 2.create VM connected to such portgroup on ovs-network 3.start domain Actual results: error: unsupported configuration: an interface connecting to network 'ovs-network' is requesting a vlan tag, but that is not supported for this type of network Expected results: domain start Additional info:
The issue can be reproduced in git tag v5.5.0, but not in v5.4.0. The problem seems to be related to changes in network/bridge_driver.c, in networkAllocatePort function.
I'm investigating the regression....
This patch should fix it https://www.redhat.com/archives/libvir-list/2019-August/msg00201.html
Yes, fixed! Thanks.
Actually, per https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_status the UPSTREAM state is for bugs that have been forwarded to an upstream tracker. This is the upstreamest tracker of them all for libvirt. The bug was fixed by: commit 93c1d5fe7bb7a62ef884eb41b505b2809d1704b6 Author: Daniel P. Berrangé <berrange> CommitDate: 2019-08-08 14:16:22 +0100 network: fix ability to use openvswitch with vlans Use the correct enum constant when validating vlan usage. This fixes a merge error in commit 6cb0ec48bd95c95489a987e05a88e8bcf1f9109c Author: Daniel P. Berrangé <berrange> Date: Mon Sep 3 17:34:22 2018 +0100 network: convert networkAllocateActualDevice to virNetworkPortDef Reviewed-by: Michal Privoznik <mprivozn> Signed-off-by: Daniel P. Berrangé <berrange> git describe: v5.6.0-81-g93c1d5fe7b which will be released in libvirt-5.7.0