Bug 1753286 - VM Start, Stop and Migrate actions not available when any VM in a namespace is being imported
Summary: VM Start, Stop and Migrate actions not available when any VM in a namespace i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Marek Libra
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-18 14:18 UTC by Radim Hrazdil
Modified: 2019-10-16 06:41 UTC (History)
4 users (show)

Fixed In Version: 4.2.0-0.nightly-2019-08-08-032431
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot (5.42 KB, image/png)
2019-09-18 14:18 UTC, Radim Hrazdil 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:45 UTC

Description Radim Hrazdil 2019-09-18 14:18:21 UTC 
Created attachment 1616257 [details]
Screenshot

Description of problem:
When there is a VM importing in certain namespace, all other VMs IN THIS NAMESPACE cannot be Started, Restarted, Migrated or stopped. Only Delete action is available.
Actions for VMs in other namespaces are available as expected.


Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-17-232025
HCO 2.1.0-47

How reproducible:
100%

Steps to Reproduce:
1. Have a VM in importing state
2. Try to start/restart/stop/migrate other VM in the same namespace
3.

Actual results:


Expected results:


Additional info:
Comment 1 Marek Libra 2019-09-18 14:19:29 UTC 
Patch: https://github.com/openshift/console/pull/2762
Comment 2 Guohua Ouyang 2019-10-10 00:31:57 UTC 
verified on console 4.2.0-0.nightly-2019-10-06-011148.
Comment 3 errata-xmlrpc 2019-10-16 06:41:33 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, 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/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.