-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
False
-
CLOSED
-
Undefined
-
CNV Virtualization Sprint 204, CNV Virtualization Sprint 205, CNV Virtualization Sprint 206
-
Important
-
No
Description of problem:
A customer tried to stop hundreds of VMs which were in scheduling and pending states using virtctl.
This did not work, because virtctl said that they are not running. This is true, but even if they are not running, virtctl should be capable of setting the state to stopped.
Version-Release number of selected component (if applicable):
2.6.3
How reproducible:
Always
Steps to Reproduce:
1. Start a VM
2. Wait for it to be in pending or scheduling state
3. Stop the VM with virtctl stop …
Actual results:
virtctl stop … fails with "VM is not running"
Expected results:
virtctl stop … succeeds
Additional info: