Description of problem:
non-VM network appears in the new vNIC profile drop down .
When creating non-VM network, it has no vNIC profile, but when going to the vNIC profiles tab, this network is appears in the new vNIC profile drop down list, but it shouldn't, because this network is a non-VM network. When trying to create new vNIC profile to this network we fail with error validation:
"Error while executing action: Cannot add VM network interface profile. VM network interface profiles cannot be added to a non-VM network. Please make sure the network is a VM network."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create non-VM network net1
2. Go to vNIC profile tab
3. net1 appears in the drop down list for new vNIC profile
net1 is available for new vNIC profile
net1 is a non-VM network and should not be available for new vNIC profile creation
Created attachment 1428837 [details]
Michael, can you tell which Engine version introduced this regression?
Ales, could this be a very recent regression due removing OvS networks from this list?
(In reply to Dan Kenigsberg from comment #2)
> Michael, can you tell which Engine version introduced this regression?
> Ales, could this be a very recent regression due removing OvS networks from
> this list?
I think this bug is exist from the very beginning of the new UI re-design. Because on 4.1 and older versions we didn't had such option or flow.
In the new UI in 4.2 we have a new vNIC profile tab and such flow is possible and it's why i think it don't a regression bug. I have missed this flow in 4.2 until now.
BTW, what do you mean removing ovs networks from this list?(i'm not aware of this), how can you know if it's an ovs network?(because it's in an ovs cluster?)
This is not affected by the auto-define. The auto-define is not yet in d/s build as well as auto-define did not touch this part of flow. I agree with Micheal that this is caused by the redesign.
Verified on - 4.2.4-0.1.el7
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.