Bug 854888 - [SetupNetworks] Can attach VLAN network with custom MTU with NON_VM network on the same nic/BOND
Summary: [SetupNetworks] Can attach VLAN network with custom MTU with NON_VM network ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-06 08:44 UTC by Meni Yakove
Modified: 2016-02-10 19:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-09 12:23:21 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine.log (6.90 MB, text/x-log)
2012-09-06 08:44 UTC, Meni Yakove
no flags Details

Description Meni Yakove 2012-09-06 08:44:05 UTC
Created attachment 610226 [details]
engine.log

Description of problem:
UI allow to attach VLAN network with custom MTU to nic/BOND that already have NON_VM network with custom MTU.
For any non VLAN network this operation blocked by UI.

Version-Release number of selected component (if applicable):
rhevm-3.1.0-15.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1.Create two networks, NON_VM_MTU_5000 and VM_VLAN_MTU_9000
2.Assign both networks to nic  

  
Actual results:
Should be blocked by UI

Expected results:
UI allow to attach both networks.

Comment 1 lpeer 2012-09-09 06:32:38 UTC
1. In which version did you find the bug? (please make sure to always specify that when you report a bug)
2. Is it blocked by the backend?

Comment 2 Meni Yakove 2012-09-09 11:27:14 UTC
1. Version-Release number of selected component (if applicable):
rhevm-3.1.0-15.el6ev.noarch
2. It is blocked by the backend.

If the decision is not to block the operation on the UI so this BUG should be closed.

Comment 3 lpeer 2012-09-09 12:23:21 UTC
At this point we have decided not to block any MTU related issue in the UI.
Adding the validation code for MTU makes the logic in the UI more complicated.

Since this operation is blocked in the engine, we'll avoid adding this logic in the UI for the time being.


Note You need to log in before you can comment on or make changes to this bug.