Bug 1694176 - [v2v] Migration failing randomly with undefined method 'ems_ref' error
Summary: [v2v] Migration failing randomly with undefined method 'ems_ref' error
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Fabien Dupont
QA Contact: Yadnyawalk Tale
Red Hat CloudForms Documentation
URL:
Whiteboard: v2v
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-29 17:20 UTC by Yadnyawalk Tale
Modified: 2019-04-15 15:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-15 15:12:42 UTC
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
automate.log (9.56 KB, text/plain)
2019-04-15 10:50 UTC, Yadnyawalk Tale
no flags Details

Description Yadnyawalk Tale 2019-03-29 17:20:52 UTC
Description of problem:
Migration failing randomly with undefined method 'ems_ref' error


Version-Release number of selected component (if applicable):
5.10.2.2.20190319204241_4304a7d 


How reproducible:
100%


Steps to Reproduce:
1. Migrate vm on QE's vmware67-ims and OSP 
2. Sometimes it is failing with ems_ref error

Last time we got such error was due to provider/host refresh issue but we tried with multiple fresh appliances too but it is not the case.


Actual results:
https://paste.fedoraproject.org/paste/Mm4RO8g1Ug2Gst7XalEU4w


Expected results:
Migration should just work


Additional info:
https://gitter.im/ManageIQ/v2v?at=5c94fb1981b15c5e4b6b616b
https://gitter.im/ManageIQ/v2v?at=5c9a2a1f8126720abc47bfbd

Comment 3 Sudhir Mallamprabhakara 2019-04-03 14:18:15 UTC
Can you please provide more information.. logs/steps/BZ created for provider/host.

Comment 4 Yadnyawalk Tale 2019-04-03 15:50:00 UTC
Actually, there was no specific steps, OSP migration was failing on any random time.
This are the automate logs we got from last failure https://paste.fedoraproject.org/paste/Mm4RO8g1Ug2Gst7XalEU4w

Devel can use appliance mentioned in Comment #2 for further investigation.
Currently we are confuse on weather this is infra issue or the actual bug since we are getting it randomly.

Comment 8 Yadnyawalk Tale 2019-04-15 10:50:43 UTC
Created attachment 1555185 [details]
automate.log

Comment 10 Yadnyawalk Tale 2019-04-15 15:12:42 UTC
Most of the time while testing I click `next` button after selecting vm tab, so when we do it very fast (click-click-click) it don't select flavor and default security group.
I just created plan once again with "patience" and it is just working. Thanks for confirming @fabien.

Closing it since it works for me.


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