Bug 1688992 - [v2v] Migration fails with backend job time out
Summary: [v2v] Migration fails with backend job time out
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.2
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.11.0
Assignee: Fabien Dupont
QA Contact: Yadnyawalk Tale
Red Hat CloudForms Documentation
URL:
Whiteboard: v2v
Depends On:
Blocks: 1683439 1690076
TreeView+ depends on / blocked
 
Reported: 2019-03-14 20:48 UTC by Yadnyawalk Tale
Modified: 2019-12-13 15:09 UTC (History)
2 users (show)

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

Attachments (Terms of Use)

Description Yadnyawalk Tale 2019-03-14 20:48:45 UTC 
Description of problem:
False alarm - Migration fails with backend job time out


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


How reproducible:
100%


Steps to Reproduce:
1. Migrate vm to rhv
(Actually we did it with @Fabien's patch https://github.com/ManageIQ/manageiq-content/pull/513)


Actual results:
It fails with exception in automate log

```
[----] E, [2019-03-14T15:21:12.378570 #20116:3b8f58] ERROR -- : Q-task_id([r1_service_template_transformation_plan_task_1]) State=<State5> running  raised exception: <number of retries <1501> exceeded maximum of <1500>>
```

Expected results:
Migration should just work.


Additional info:
Related discussion - https://gitter.im/ManageIQ/v2v?at=5c8ab7d2d1e7281f092c3a5a
Comment 2 James Wong 2019-03-18 12:34:52 UTC 
PR: https://github.com/ManageIQ/manageiq/pull/18557
Comment 4 James Wong 2019-03-26 18:00:29 UTC 
PR: https://github.com/ManageIQ/manageiq/pull/18597
Comment 5 James Wong 2019-03-26 18:01:25 UTC 
sorry, modified the wrong bug :(

Resetting it...
Comment 6 Yadnyawalk Tale 2019-06-14 12:34:17 UTC 
Fixed! Verified on: 5.11.0.8.20190611155126_01e077e

Please note 5.11.0.8 don't have v2v-conversion-ansible package and hence migration not working with that but I have installed package manually and migration is working.
We are tracking that issue under BZ1720614.
Note You need to log in before you can comment on or make changes to this bug.