Bug 1718678 - [v2v] Cancel of VMware to RHV VMs migration does not actually cancel
Summary: [v2v] Cancel of VMware to RHV VMs migration does not actually cancel
Keywords:
Status: CLOSED DUPLICATE of bug 1666799
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Fabien Dupont
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-09 20:05 UTC by Ilanit Stein
Modified: 2019-06-11 14:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-11 13:52:06 UTC
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Conversion host #1 v2v import and wrapper logs (4.77 MB, application/zip)
2019-06-09 20:10 UTC, Ilanit Stein
no flags Details
Conversion host #2 v2v import and wrapper logs (5.97 MB, application/zip)
2019-06-09 20:12 UTC, Ilanit Stein
no flags Details

Description Ilanit Stein 2019-06-09 20:05:04 UTC
Description of problem:
I run VMware->RHV 10 VMs VMs migration, and few minutes are triggering the migration plan, I cancelled it, via CFME UI, (mark all VMs and pressed Cancel).

I cancelled it, because I realized that the conversion hosts max_concurrent tasks was set to nil, and not to 5, as I needed. 
After cancellation, I removed the migration plan.

I edited the conversion hosts max_concurrent_tasks to 5, via Restapi.
After about 15 minutes, I created & run a new migration plan.

Seems that the first migration plan run, had affect on the second migration plan.

Migration details:
10 VMs, with 100GB Disk (66% usage), migrated from a single VMware host, VDDK, using 2 conversion hosts, with max_concurrent_tasks=5 each.

Result:
- On RHV side, there are 8 VMs imported successfully (duration: 2:40)
v2v_migration_vm_0 
v2v_migration_vm_1 
v2v_migration_vm_2 
v2v_migration_vm_3 
v2v_migration_vm_5 
v2v_migration_vm_7
v2v_migration_vm_8
v2v_migration_vm_9
- On CFME UI, it is reported that only 5 out of 10 VMs migrated successfully.
 
Checked v2v import logs in the conversion hosts, now that the VM migration has ended:

* Conversion host #1 (7 log files):
v2v_migration_vm_0, 1, 4 failed. Last updated @ 17:30
v2v_migration_vm_0, 5, 3, 2 passed. Last updated @ 19:30

* Conversion host #2: (7 log files):

v2v_migration_vm_6 failed. Last updated @ 17:30
v2v_migration_vm_3, 2, 1, 7, 9, 8 passed. Last updated @ 18:49-19:34


Version-Release number of selected component (if applicable):
CFME-5.10.5.1/RHV-4.3.4

Expected results:
Cancel migration, should indeed cancel the migration.

Comment 2 Ilanit Stein 2019-06-09 20:10:16 UTC
Created attachment 1578864 [details]
Conversion host #1 v2v import and wrapper logs

Comment 3 Ilanit Stein 2019-06-09 20:12:04 UTC
Created attachment 1578865 [details]
Conversion host #2 v2v import and wrapper logs

Comment 4 Fabien Dupont 2019-06-11 10:26:50 UTC
Isn't it a duplicate of bug 1666799 ?

Comment 5 Ilanit Stein 2019-06-11 13:49:23 UTC
(In reply to Fabien Dupont from comment #4)
> Isn't it a duplicate of bug 1666799 ?

Yes it is. Marking bug as such.

Comment 6 Ilanit Stein 2019-06-11 13:52:06 UTC

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


Note You need to log in before you can comment on or make changes to this bug.