Description of problem: If you create range 200-300 on Neutron and create a network with VLAN 10 the action succeeds Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create external network from Ovirt 2. Pick up a VLAN 10 for that vlan when the Vlan range on Neutron is 200-300 3. Actual results: The network is created with VLAN 200 on Neutron Expected results: The action should be blocked because incorrect VLAN (not from the range) was picked up Additional info:
It seems like API is using tenant networks, instead of using provider network. Provider network has the ability to specify the exact VLAN from RHEV into Neutron. In case the VLAN is not in the range the API return error , and network creations MUST fail Moving severity to HIGH, since if user create network with VLAN 10 and actually it is not created to NO network at all ( don't forget the switchs on the way are configured to allow specific range of vlans on hosts )
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
I think for starters, when creating an external network with a VLANs based network provider, we should hide / disable the VLAN field. Later, we can consider the creation of provider networks, and enhance the GUI so that it is more clear and understandable.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
The label must be specified when user selects a specific VLAN ID. A user might, however, choose a label but not a specific VLAN ID.
Verified in 3.5.0-0.0.master.20140722232058.git8e1babc.el6
oVirt 3.5 has been released and should include the fix for this issue.