Bug 1105842

Summary: [Neutron integration] Custom device properties are not passed to vdsm
Product: [Retired] oVirt Reporter: Moti Asayag <masayag>
Component: ovirt-engine-coreAssignee: Moti Asayag <masayag>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.5CC: bugs, gklein, iheim, myakove, rbalakri, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: ovirt-engine-3.5.0_beta Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:24:38 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:
Bug Depends On:    
Bug Blocks: 1154674    

Description Moti Asayag 2014-06-08 06:35:10 UTC
Description of problem:
When a vm interface is being attached to an external network, engine should provide the custom properties as defined on the nic's profile.

However, due to internal implementation, the network devices as configured on the vm, failed to be identified at run-time.

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


How reproducible:
always

Steps to Reproduce:
1. Add external network EXNET
2. Assing the vnic profile EXNET to a vm.
3. Start the VM

Actual results:
No custom properties are provided to vdsm 'create' vm verb, hence vm failed to start.

Expected results:
The custom element should contain the external provider and its network details, i.e.:

'custom': {'plugin_type': 'OPEN_VSWITCH', 'security_groups': 'd37cd9aa-6eed-4bdc-b4c4-31b5aecf6048', 'vnic_id': 'f2572c9d-c9e9-44ba-9ebe-7be383aeb2f1', 'provider_type': 'OPENSTACK_NETWORK'}

Additional info:

Comment 1 GenadiC 2014-08-07 08:43:21 UTC
Verified in 3.5.0-0.0.master.20140804172041.git23b558e.el6

Comment 2 Sandro Bonazzola 2014-10-17 12:24:38 UTC
oVirt 3.5 has been released and should include the fix for this issue.