Bug 1473169

Summary: [v2v] Failures/Errors are not reflected at all in the Automate request messages
Product: Red Hat CloudForms Management Engine Reporter: Ilanit Stein <istein>
Component: ProvidersAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: gblomqui, jfrey, jhardy, michal.skrivanek, nsimsolo, obarenbo, tjelinek
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: rhev:v2v
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1479414 (view as bug list) Environment:
Last Closed: 2018-03-06 14:46:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: RHEVM Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1479414    
Attachments:
Description Flags
vdsm.log
none
import log none

Description Ilanit Stein 2017-07-20 07:37:10 UTC 
Description of problem:
When there are failures in the import of VM, from VMWare to RHV, It is not reflected in the CFME Automate->Request. 
The Request last message keeps having Message [Checking for VM Import completion] Current Retry Number [...].

Examples:
1. When running v2v for a Windows VM that has snapshots, which is not possible.
On vdsm.log, this error is seen:
"2017-07-19 15:31:22,081+0300 ERROR (jsonrpc/7) [root] vm 'win7_auto' has snapshots and therefore can not be imported since snapshot conversion is not supported for VMware (v2v:176)"
(See vdsm.log attached)

2. When v2v fail for a Windows VM on the following error (taken from v2v import log):
"virt-v2v: error: unable to mount the disk image for writing. This has
probably happened because Windows Hibernation or Fast Restart is being used
in this guest. You have to disable this (in the guest) in order to use
virt-v2v."
(See import log attached)

Source VM name: "win10_IDE"


** Indeed those errors are not seen in the engine.log, but in engine.log,
it is mentioned that the import/convert failed, and even that is not propagated to CFME.

Version-Release number of selected component (if applicable):
CFME-5.8.1 + several fixes for v2v bugs/RHV-4.1
Comment 2 Ilanit Stein 2017-07-20 07:42:45 UTC 
Created attachment 1301555 [details]
vdsm.log
Comment 3 Ilanit Stein 2017-07-20 07:43:08 UTC 
Created attachment 1301557 [details]
import log
Comment 4 Tomas Jelinek 2017-08-04 12:47:43 UTC 
patches posted:
https://github.com/ManageIQ/manageiq-content/pull/161
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/73
Comment 6 Ilanit Stein 2018-01-02 07:37:12 UTC 
Verified on CFME-5.9.0.14/RHV-4.1.8,
that the message in the request indicate import failed:

* When destination VM name already exist (Seen in engine.log):
[EVM] VM [mb-win10] Step [Launch] Status [Error submitting VM Import to RHV] Message [Submitting VM Import to RHV]

* When windows VM import failed on mount problem (seen in the host vdsm/import log):
[EVM] VM [tg-win10] Step [WaitForImport] Status [Error encountered during VM import] Message [Checking for VM Import completion]