Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1525353

Summary: vNIC mapping is broken on import from data domain - vNICs mapped as 'Empty' in the destination cluster
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: eraviv
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2.0CC: bugs, danken, lveyde, ylavi
Target Milestone: ovirt-4.2.1Keywords: Regression, ZStream
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.1.2 Doc Type: Bug Fix
Doc Text:
undefined
Story Points: ---
Clone Of:
: 1530565 (view as bug list) Environment:
Last Closed: 2018-02-12 11:48:15 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: 1536966    
Bug Blocks: 1530565    
Attachments:
Description Flags
record1
none
engine log
none
engine failedQA
none
expected behavior in various scenarios affected by this bug as agreed by dev+qe none

Description Michael Burman 2017-12-13 07:11:06 UTC
Description of problem:
vNIC mapping is broken on import from data domain - vNICs mapped as 'Empty' in the destination cluster.

We have a new regression for the vNIC mappings from data domain. It seems that the vNIC are mapped as 'Empty' on the destination target.

Version-Release number of selected component (if applicable):
4.2.1-0.0.master.20171211205712.git7b1f4d1.el7.centos

- It is 100% reproducible if you press the 'vNIC Profiles Mapping'(and close it without a change) button prior approving the import operation. 

Steps to Reproduce:
1. Import VM/Template from data domain with some vNICs and different profiles without re-assigning new or different profiles for the destination cluster. Before approving press on the 'vNIC Profiles Mapping' button and close it and then Just import as it is.

Actual results:
All vNICs are mapped as 'Empty' in the destination cluster. 

Expected results:
Must work as expected.

Comment 1 Michael Burman 2017-12-13 07:12:01 UTC
The bug is the d/s build as well 4.2.0.2-0.1.el7

Comment 2 Michael Burman 2017-12-13 07:14:31 UTC
Created attachment 1367104 [details]
record1

Comment 3 Michael Burman 2017-12-13 07:16:36 UTC
Created attachment 1367105 [details]
engine log

Comment 4 Red Hat Bugzilla Rules Engine 2017-12-13 07:22:30 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 5 Michael Burman 2017-12-13 07:42:35 UTC
Note for my self and dev - 

- Another vise-versa flow is:
import vm or template with 3 vNICs, all mapped as 'Empty' in the origin prior import. Remap only 1 nic on target to some profile9ovirtmgmt) and keep other 2 nics as empty.
After import all 3 nics will imported with the first nic's profile(ovirtmgmt).

Comment 6 Michael Burman 2017-12-13 07:51:49 UTC
(In reply to Michael Burman from comment #5)
> Note for my self and dev - 
> 
> - Another vise-versa flow is:
> import vm or template with 3 vNICs, all mapped as 'Empty' in the origin
> prior import. Remap only 1 nic on target to some profile9ovirtmgmt) and keep
> other 2 nics as empty.
> After import all 3 nics will imported with the first nic's
> profile(ovirtmgmt).

Note for my self and dev, please ignore this flow and comment as it's expected)))

Comment 7 Dan Kenigsberg 2017-12-13 11:12:31 UTC
Postponing to 4.2.1, as this does not seem to affect the Ansible-driver disaster-recovery flow.

Comment 8 Michael Burman 2018-01-01 13:44:31 UTC
What about a fix for 4.1? this bug should be cloned to 4.1 as it exist in 4.1 for VMs flow.

Comment 9 Dan Kenigsberg 2018-01-03 11:10:36 UTC
Yaniv Lavi wants this in

Comment 11 Michael Burman 2018-01-07 12:22:27 UTC
The bug not in the latest d/s build or wasn't properly fixed. Any how it failedQa on 4.2.1-0.2.el7

The fix should have been in this build.

Comment 12 Michael Burman 2018-01-07 12:23:45 UTC
Created attachment 1378056 [details]
engine failedQA

Comment 13 eraviv 2018-01-10 08:03:50 UTC
Created attachment 1379378 [details]
expected behavior in various scenarios affected by this bug as agreed by dev+qe

Comment 14 Michael Burman 2018-01-22 07:26:51 UTC
Can't test the template flow and VMs flow properly as i'm blocked with new bug - 
BZ 1536966

Comment 15 Michael Burman 2018-01-25 13:54:26 UTC
Verified on - 4.2.1.3-0.1.el7

Comment 16 Sandro Bonazzola 2018-02-12 11:48:15 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.