Bug 2012562 - migration condition is not detected in list view
Summary: migration condition is not detected in list view
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Yaacov Zamir
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-10-10 09:59 UTC by Yaacov Zamir
Modified: 2022-03-10 16:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:18:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
No migration condition in vm list view (531.12 KB, image/gif)
2021-10-10 09:59 UTC, Yaacov Zamir
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10205 0 None open Bug 2012562: Check for migration condition before default unknown status 2021-10-10 10:02:34 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:19:10 UTC

Description Yaacov Zamir 2021-10-10 09:59:35 UTC
Created attachment 1831435 [details]
No migration condition in vm list view

Description of problem:
When in list view, migration condition is not detected

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

How reproducible:

Steps to Reproduce:
1. go to vm list view
2. start migration of a running vm
3. wait for migration condition

Actual results:
vm does not show any condition while migrating

Expected results:
vm show migration condition while migrating

Additional info:
the action menu is also broken because of the missing condition

Comment 4 Guohua Ouyang 2021-10-21 07:31:56 UTC
verified on master

Comment 7 errata-xmlrpc 2022-03-10 16:18:42 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.10.3 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.