Bug 1870174 - Start Virtual Machine option not available during CDI import
Summary: Start Virtual Machine option not available during CDI import
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.6.0
Assignee: Phillip Bailey
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-19 13:25 UTC by Phillip Bailey
Modified: 2020-10-27 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:29:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6375 0 None closed Bug 1870174: Add start VM option during CDI import 2020-12-13 11:38:18 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:29:27 UTC

Description Phillip Bailey 2020-08-19 13:25:50 UTC
Description of problem:
The start option is not available in action drop down menus when a VM is in the importing (CDI) state.


How reproducible:
100%

Steps to Reproduce:
1. Create a VM that requires CDI import
2. Start VM and wait for the status to read "Importing (CDI)"
3. Click on the kebab menu for the VM in the list view or the Actions menu from the VM's detail view and look for the "Start Virtual Machine" option

Actual results:
The start option is not displayed

Expected results:
The start option should be available

Additional info:
The user should be warned that the VM will not start until the import completes and the choice cannot be changed.

Comment 4 errata-xmlrpc 2020-10-27 16:29:12 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 (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.

https://access.redhat.com/errata/RHBA-2020:4196


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