Bug 1680487 - [v2v][RHV] Migration to RHV failed, with Status: Assess Migration
Summary: [v2v][RHV] Migration to RHV failed, with Status: Assess Migration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.11.0
Assignee: Fabien Dupont
QA Contact: Shveta
Red Hat CloudForms Documentation
URL:
Whiteboard: v2v
Depends On:
Blocks: 1686049
TreeView+ depends on / blocked
 
Reported: 2019-02-25 07:40 UTC by Ilanit Stein
Modified: 2019-12-13 15:09 UTC (History)
5 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1686049 (view as bug list)
Environment:
Last Closed: 2019-12-13 15:09:56 UTC
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Migration_fail_screenshot.png (85.99 KB, image/png)
2019-02-25 07:40 UTC, Ilanit Stein
no flags Details
Migration_fail_screenshot_info.png (85.28 KB, image/png)
2019-02-25 07:41 UTC, Ilanit Stein
no flags Details

Description Ilanit Stein 2019-02-25 07:40:17 UTC
Description of problem:
On CFME-5.10.1.2/RHV-4.3.1 (Small scale),
v2v single VM migration do not even start, though conversion host exist.

The UI migration progress bar show that 0 disk was copied,
There is no log to download.
This is the message seen:
VM migrations failed
Status: Assess Migration "i" (See attached "Migration_fail_screenshot.png") 
Pointing with cursor, on the "i" icon show: 
 Start Time: February 24th 2019, 8:32 pm 
(See attached "Migration_fail_info_screenshot.png")

There is one conversion host on CFME:
https://<CFME_FQDN>/api/conversion_hosts/1

{"href":"https://<CFME_FQDN/api/conversion_hosts/1","id":"1","name":"<Conversion host fqdn>","address":null,"type":null,"resource_type":"Host","resource_id":"5","version":null,"max_concurrent_tasks":null,"vddk_transport_supported":true,"ssh_transport_supported":null,"created_at":"2019-02-24T18:25:49Z","updated_at":"2019-02-24T18:25:49Z","concurrent_transformation_limit":null,"cpu_limit":null,"memory_limit":null,"network_limit":null,"blockio_limit":null,"actions":[{"name":"edit","method":"post","href":"https://CFME_FQDN/api/conversion_hosts/1"},{"name":"delete","method":"post","href":"https://CFME_FQDN/api/conversion_hosts/1"},{"name":"delete","method":"delete","href":"https://CFME_FQDN/api/conversion_hosts/1"}]}


Version-Release number of selected component (if applicable):
CFME-5.10.1.2
RHV-4.3.1.1-0.1.el7

How reproducible:
Tried to do v2v migration of a single VM twice, and it failed the same.

Additional info:
This bug do not occur on CFME-5.10.1.1

Comment 3 Ilanit Stein 2019-02-25 07:40:47 UTC
Created attachment 1538326 [details]
Migration_fail_screenshot.png

Comment 4 Ilanit Stein 2019-02-25 07:41:12 UTC
Created attachment 1538327 [details]
Migration_fail_screenshot_info.png

Comment 5 Ilanit Stein 2019-02-26 15:46:29 UTC
This might be related to: 
Bug 1668720 - [RHV] CFME fail to refresh\discover RHV-4.3.
But note that though Bug 1668720 also exists on CFME versions, prior to 5.10.1.2,
v2v migration from VMware to RHV was successful.

Comment 6 Fabien Dupont 2019-02-27 15:40:13 UTC
https://github.com/ManageIQ/manageiq/pull/18496

Comment 8 Yadnyawalk Tale 2019-06-14 13:26:27 UTC
Verified on: 5.11.0.8.20190611155126_01e077e


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