Bug 1851886 - [CNV][V2V] VMWare pod is failing when running wizard to migrate from RHV
Summary: [CNV][V2V] VMWare pod is failing when running wizard to migrate from RHV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: V2V
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.4.0
Assignee: Piotr Kliczewski
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-29 10:18 UTC by Igor Braginsky
Modified: 2020-07-28 19:10 UTC (History)
6 users (show)

Fixed In Version: v2.4.0-18
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 19:10:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of an error (49.24 KB, image/png)
2020-06-29 10:18 UTC, Igor Braginsky 		no flags Details
Log file of the pod (20.36 KB, application/octet-stream)
2020-06-29 10:20 UTC, Igor Braginsky 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github ManageIQ manageiq-v2v-conversion_host pull 77 0 None closed Handle missing vnicProfiles 2020-07-13 18:22:55 UTC
Red Hat Product Errata RHSA-2020:3194 0 None None None 2020-07-28 19:10:50 UTC

Description Igor Braginsky 2020-06-29 10:18:06 UTC 
Created attachment 1699112 [details]
Screenshot of an error

Description of problem:VMWare pod is failing when running wizard to migrate from RHV. Example of UI message:

back-off 40s restarting failed container=v2v-vmware pod=v2v-vmware-bbb4d9588-82gpv_igor-test(68b1c91b-6ff8-410f-b135-b2a3addb21ce). Please inspect a failing pod v2v-vmware

See attachments for a screenshot and logs


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


How reproducible: from time to time


Steps to Reproduce:
1. Run wizard
2. Take an existing RHV instance to migrate from
3. Select cluster, VM
4. Click `Next` button quickly, while VM details are loading 

Actual results:
One gets an exception


Expected results:



Additional info:
Comment 1 Igor Braginsky 2020-06-29 10:20:58 UTC 
Created attachment 1699114 [details]
Log file of the pod
Comment 2 Ilanit Stein 2020-07-02 06:59:03 UTC 
Apparently this bug is happening when trying to import a VM that has a nic,
but it's vnic profile is empty.

I have reproduced it.
Comment 3 Ilanit Stein 2020-07-02 07:16:09 UTC 
After waiting couple of minutes the v2v-vmware pod that has crashed is lunched successfully.
Comment 4 Ilanit Stein 2020-07-08 14:52:51 UTC 
Verified on CNV-2.4 from July 07.

VM import of a VM with nic that has an empty vnic profile is imported successfully, and not causing the v2v-vmware pod to crash.
Comment 7 errata-xmlrpc 2020-07-28 19:10:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:3194
Note You need to log in before you can comment on or make changes to this bug.