Bug 1952372 - VM stop action should not be there if the VM is not running
Summary: VM stop action should not be there if the VM is not running
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Gilad Lekner
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-22 07:27 UTC by Guohua Ouyang
Modified: 2021-07-27 23:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 23:02:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
cannot stop a pending VM (1.15 MB, application/octet-stream)
2021-04-22 07:27 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 8766 0 None open Bug 1952372: VM stop action should not be there if the VM is not running 2021-04-25 13:36:54 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:03:13 UTC

Description Guohua Ouyang 2021-04-22 07:27:53 UTC
Created attachment 1774338 [details]
cannot stop a pending VM

Description of problem:
When a VM is in pending state(wait for resources), the stop action should not be there because it cannot stop the VM. 

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

How reproducible:

Steps to Reproduce:
1. Have a VM in pending state
2. Try to stop the VM

Actual results:
VM cannot be stopped because the VM is not running

Expected results:
No stop in action list

Additional info:

Comment 4 errata-xmlrpc 2021-07-27 23:02:52 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.