Description of problem: There is an 'Importing' state of a VM. I have not seen that one documented anywhere. Nevertheless, in Actions there are options to stop/restart and delete that machine (Which is also not documented in [1], e.g.). Stop and Delete works fine, but Restart returns an error: "<name> not found." Version-Release number of selected component (if applicable): oc v3.11.69 kubernetes v1.11.0+d4cacc0 How reproducible: always Steps to Reproduce: 1. Create a virtual machine, and choose Container as a provision source 2. Start that machine, observe Importing... 3. Choose Restart in Actions Actual results: An error machine is not found. Expected results: There should be smth about Importing in docs, and no error on Reboot. Or maybe even no Stop/Restart actions, if those are not applicable (are they?), before image import. Additional info: [1] https://github.com/openshift/openshift-docs/blob/61a051b762659b05377301e9aca5df764ab3418a/modules/cnv_vm_actions_web.adoc#cnv-vm-actions-web
@Andrew: FYI, not sure if you need a separate BZ to handle it.
Tomas, I have opened a separate doc BZ 1676572
as per agreement moving this to 2.0
https://github.com/kubevirt/web-ui/pull/237
How to get a VM into importing status? I see it once and the restart option is not available when vm is importing. But for status "pending", "Importer Error", the problem "VM not found" is still there, I think "restart" should be disabled for these status as well. And "migration" should be disabled since the VM is not existed yet.
How to get a VM into importing status? I see it once and the restart option is not available when vm is importing. -> Vm is in importing status when you use URL source and import didn't complete yet https://github.com/kubevirt/web-ui/pull/375
Restart and Migration are not available in vm actions when vm in importing.
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/RHEA-2019:1850