Bug 1067469

Summary: [Neutron integration] The Neutron network UUID should be the ID of the network on RHEV
Product: [Retired] oVirt Reporter: GenadiC <gcheresh>
Component: ovirt-engine-coreAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, gklein, iheim, oblaut, yeylon
Target Milestone: ---Keywords: Triaged, UserExperience
Target Release: 3.4.1   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: av3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 13:38:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1063716    

Description GenadiC 2014-02-20 13:57:33 UTC
Description of problem:
If you create a network from RHEV on RHEV and Neutron or if you import Neutron Network to RHEV, the UUID of Neutron network is not reflected on RHEV. It has network ID that is different from UUID.

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


How reproducible:
Always

Steps to Reproduce:
1. Import Neutron Network to Ovirt (or create a new one on Ovirt and Neutron)
2. Check the UUID on Neutron and network ID on Ovirt
3.

Actual results:
IDs have different values

Expected results:
ID should be the same

Additional info:

Comment 1 Moti Asayag 2014-02-20 19:24:19 UTC
The expected result aren't accurate:

The neutron's network UUID is stored on network.provider_network_external_id.
It should appear in the UI as the network external id on the network's general sub-tab.

Comment 2 Sandro Bonazzola 2014-03-04 09:22:33 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 3 GenadiC 2014-03-16 14:30:32 UTC
Verified in av3

Comment 4 Sandro Bonazzola 2014-05-08 13:38:10 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.