Bug 824870

Summary: [RHEVM] [backend] [Setup Host Networks] cannot add VLAN to bonded interface
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engineAssignee: lpeer <lpeer>
Status: CLOSED DUPLICATE QA Contact: Martin Pavlik <mpavlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: dyasny, gklein, iheim, lpeer, mkolesni, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-02 09:18:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of error message none

Description Martin Pavlik 2012-05-24 13:30:25 UTC 
Created attachment 586634 [details]
screenshot of error message

Description of problem:
if user tries to attach VLAN network via Setup Host Networks dialog, 
error:  The specified Logical Network doesn't exist.
appears

Version-Release number of selected component (if applicable):
oVirt Enterprise Virtualization Engine Manager Version: 3.1.0_0001-11.el6ev 

How reproducible:
100%

Steps to Reproduce:
1. crate network with VLAN tagging
2. go to Hosts-> your host -> Setup Host Networks
   a) create bond, set bond to mode1
   b) drag VLAN from step 1 over new bond interface, click OK


Actual results:
error:  "The specified Logical Network doesn't exist." appears

Expected results:
VLAN should be added to bonded interface with no error

Additional info:
bug might be related bug 824803

only on line is logged to engine.log

2012-05-24 15:24:26,304 WARN  [org.ovirt.engine.core.bll.SetupNetworksCommand] (ajp--0.0.0.0-8009-7) [38893d16] CanDoAction of action SetupNetworks failed. Reasons:NETWROK_NOT_EXISTS
Comment 1 Mike Kolesnik 2012-07-02 09:18:49 UTC 

*** This bug has been marked as a duplicate of bug 826401 ***