Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a VM from URL source, do not click start after creation
2. Navigate to detail
=> VM is in Off state
3. Start VM
=> VM is in Pending state
VM should report Importing
is "Importing" is used for importing VM from RHV/VMware, can we use a word to distinct from importing VM from RHV/VMware?
@Matt: hmmm, do you think it is a problem to call it "importing" both for v2v import from RHV/VMware and CDI import from an URL?
In my opinion, if there is no difference between "CDI import" from "RHV/Vmware import", we can place "URL" into "Import with Wizard", not "New with Wizard".
It's better to differentiate them.
Yaacov pointed out that we're also discussing the differentiation of the terminology issue in https://bugzilla.redhat.com/show_bug.cgi?id=1849555. The KubeVirt docs  use the term "import" and the CDI README  specifies importing by source. Yaacov and I think we should remain consistent with them and specify the import source, such as "Importing from URL", "Importing from VMWare", etc. If we can all agree on that, it will still leave the question of whether URL import should be in the import wizard instead of the create wizard. Filip, what do you think?
The main difference is that we are importing a VM from VMware/RHV and in case URL import it is just one DV/PVC. This complicate matters even mores since you can add such http DV/PVC to any artificial source in the wizard. So having a special wizard for that would not accomplish much IMO.
I am not against a different or more detailed naming, but I still think it is clear what is going on to some degree.
The current scheme
Importing (CDI) - this is meant for all imports http, pvc, blank,
or Import error (RHV), Import pending (RHV), etc.
Ofc, you can still see more details in the popup when you click the on the status - we can also work on that - what information we want to display there
We fixed some bugs last sprint, did not have capacity to fix this one. Setting upcoming sprint.
verified on 4.6.0-fc.4
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.