Description of problem: I am trying to configure a vNIC profile with port mirroring but i cannot because the checkboxes for the port mirroring, migratable and passthrough are grayed out and i am unable to choose any of them. Version-Release number of selected component (if applicable): 4.2.8 How reproducible: Very! Steps to Reproduce: 1.Create a new logical network 2.Go to Network/vNIC Profiles->Edit 3.On the VM Interface profile the options port mirroring, migratable and passthrough are grayed out and cannot choose any of them Actual results: The options are disabled and not choosable. Expected results: Click on the port mirroring checkbox to use it. Additional info: I am using a newly created logical network thus it is not attached to any VMs, I am using a Linux Bridge Cluster.
QE doesn't see this issue on 4.2.8.3-0.1.el7ev Any chance that you are using an external networks(OVN networks)? this options grayed out by default for external networks. native logical network behave as expected.
It might enough to have an external network defined, but the behavior might vary in different environments. Can you enable port mirroring if you open the dialog to create a new vNIC profile, select an external network before selecting a non-external one?
(In reply to Dominik Holler from comment #2) > It might enough to have an external network defined, but the behavior might > vary in different environments. > Can you enable port mirroring if you open the dialog to create a new vNIC > profile, select an external network before selecting a non-external one? I don't follow the question Dominik. please rephrase
(In reply to Michael Burman from comment #3) > (In reply to Dominik Holler from comment #2) > > It might enough to have an external network defined, but the behavior might > > vary in different environments. > > Can you enable port mirroring if you open the dialog to create a new vNIC > > profile, select an external network before selecting a non-external one? > > I don't follow the question Dominik. please rephrase My suspicion is that there is an error in the UI code, which grays out the port mirroring input depending on its previous state. The wrong rule might be, that the input keeps gray if it was gray before. One way to get there might be: 1. Network > vNIC Profiles > New 2. Select external network -> port mirroring input should be gray 3. Select non-external network -> port mirroring input should not be gray, but it is
Dominik, your flow is not legal. step 2. is not possible. you can't select external network if already under a specific network > vNIC profile > new vNIC proifle, if going this flow, the network is already chosen and grayed out. The only flow that this is possible if going directly to the vNIC profiles main section and choosing new vNIC profile, then the first network of the DC will appear in the list(alphabetic), if the first network in the DC is an external network, this properties are gray out as expected, if choosing a network that is a native one, this properties still remain as grayed out. So the bug here is: 1. Create external network a1 and native network a2 in DC1 2. Go to 'vNIC Profiles' main section 3. Press 'New' 4. The first network in the drop down list will be 'a1', the external network. All properties will be grayed out as expected 5. Choose 'a2' - result: All properties remain grayed out, but should be available for setting.
(In reply to Michael Burman from comment #5) > So the bug here is: > > 1. Create external network a1 and native network a2 in DC1 > 2. Go to 'vNIC Profiles' main section > 3. Press 'New' > 4. The first network in the drop down list will be 'a1', the external > network. All properties will be grayed out as expected > 5. Choose 'a2' - result: All properties remain grayed out, but should be > available for setting. Michael, thanks for finding this flow.
I just updated the hosted engine from 4.2.8 to 4.3 and still the issue is not fixed. Under 4.3 I edited a network interface profile using the REST API and it changed the properties to port-mirroring enabled. But when im attaching the network to VM the VM does not boot-up with the following error: VDSM node3 command DestroyVDS failed: General Exception: ('(1, \'Cannot find device "port_mirroring_"\\n\', [\'/sbin/tc\', \'filter\', \'show\', \'dev\', \'port_mirroring_test\', \'parent\', \'ffff:\'])',) p.s the network is attached to the host
(In reply to ada from comment #7) > I just updated the hosted engine from 4.2.8 to 4.3 and still the issue is > not fixed. > > Under 4.3 I edited a network interface profile using the REST API and it > changed the properties to port-mirroring enabled. > > But when im attaching the network to VM the VM does not boot-up with the > following error: > > VDSM node3 command DestroyVDS failed: General Exception: ('(1, \'Cannot > find device "port_mirroring_"\\n\', [\'/sbin/tc\', \'filter\', \'show\', > \'dev\', \'port_mirroring_test\', \'parent\', \'ffff:\'])',) > > > p.s the network is attached to the host This seems to be an additional issue. Would you please create a new bug for this and attach the relevant logfiles? Helpful would be vdsm.log containing the failed command and a call of getCapabilites, which can be triggered by "Reresh capabilites" the menu of the host in webadmin.
Verified on - 4.3.2-0.1.el7
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.2 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days