50% depending on the vm-import CR generated name
Steps to Reproduce:
1. import VM which succeeds in importing
2. delete that VM
3. import VM which fails to import (in validating phase)
4. failed VM is not visible in the VM's list
Import is shown every time
* these VMs must have a same name
Verified on CNV-2.4
Was tested with two parallel imports of same source VM.
The second VM import failed on disk locked Import Error, as expected,
and it's VM import resource was listed in the VMs view.
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.