Bug 1875287

Summary: [v2v][UI]VM import RHV to CNV: when the importer pod is in pending state, the VM looks like successfully imported
Product: OpenShift Container Platform Reporter: Tomas Jelinek <tjelinek>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Amos Mastbaum <amastbau>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: amastbau, aos-bugs, fkrepins, istein
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ux_issue
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:37:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Jelinek 2020-09-03 08:21:42 UTC 
Description of problem:
In my env the importer pod can not be started because its PVC can not be bound. But if I look at the VM list, the VM has a status "off" and there is no indication anywhere that the import is in progress (other than in the events).

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


How reproducible:


Steps to Reproduce:
1. start an import on an env where the PVC can not be bound
2. look at the VM, it's status is off
3.

Actual results:
the status is off

Expected results:
the status should be reflecting that the import is in progress

Additional info:
Comment 1 Filip Krepinsky 2020-09-03 11:02:15 UTC 
this was due to the vm-import-operator moving CRD version from alpha -> beta
Comment 5 errata-xmlrpc 2020-10-27 16:37:26 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196