Bug 1067061 - [Neutron integration] internal error ifname "vnet0" not in key map when trying to run VM with Neutron Network
Summary: [Neutron integration] internal error ifname "vnet0" not in key map when tryi...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.4.0
Assignee: Mike Kolesnik
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks: 1063716
TreeView+ depends on / blocked
 
Reported: 2014-02-19 15:18 UTC by GenadiC
Modified: 2014-03-03 08:13 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-25 14:04:45 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)
engine and vdsm log (828.18 KB, application/zip)
2014-02-19 15:19 UTC, GenadiC 		no flags Details
View All

Description GenadiC 2014-02-19 15:18:00 UTC 
Description of problem:
Start VM fails when on VM resides VNIC profile of the Network imported from Neutron (or created from Ovirt as external network)

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create external Network with Ovirt (or import one from Neutron)
2. Create VNIC profile for that network
3. Add that VNIC profile to VM
4. Start VM

Actual results:
Start VM fails

Expected results:
VM should be started as it does for non-external Network

Additional info:
Comment 1 GenadiC 2014-02-19 15:19:52 UTC 
Created attachment 865113 [details]
engine and vdsm log
Comment 2 Mike Kolesnik 2014-02-25 09:51:14 UTC 
Please reproduce with only the vnic of neutron network attached, and post libvirt log as it's (as stated) a libvirt internal error.
Comment 3 GenadiC 2014-02-25 14:04:45 UTC 
Cannot reproduce for the moment
Note You need to log in before you can comment on or make changes to this bug.