Bug 2015356 - Different status shows on VM list page and details page
Summary: Different status shows on VM list page and details page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Gilad Lekner
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks: 2088247
TreeView+ depends on / blocked
 
Reported: 2021-10-19 02:19 UTC by Guohua Ouyang
Modified: 2022-08-10 10:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:38:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vm_status_example_1 (356.81 KB, image/gif)
2021-10-19 02:19 UTC, Guohua Ouyang
no flags Details
vm_status_example_2 (4.42 KB, image/png)
2021-10-19 02:19 UTC, Guohua Ouyang
no flags Details
vm_status_example_3 (4.83 KB, image/png)
2021-10-19 02:20 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10922 0 None Merged Bug 2015356: Different status shows on VM 2022-01-28 19:14:20 UTC
Github openshift console pull 11512 0 None open Bug 2015356: Different status shows on VM list page and details page 2022-05-18 07:20:41 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:38:47 UTC

Description Guohua Ouyang 2021-10-19 02:19:02 UTC
Created attachment 1834455 [details]
vm_status_example_1

Description of problem:
Different status shows on VM list page and details page
.
Version-Release number of selected component (if applicable):
OCP 4.9.0

How reproducible:
100%

Steps to Reproduce:
1. Create a VM and start it
2. Monitor VM status on the list view page and details page
3.

Actual results:
Different status shows on VM list page and details page

Expected results:
VM list page and details page shows the consistent status.
.

Additional info:

Comment 1 Guohua Ouyang 2021-10-19 02:19:39 UTC
Created attachment 1834456 [details]
vm_status_example_2

Comment 2 Guohua Ouyang 2021-10-19 02:20:04 UTC
Created attachment 1834457 [details]
vm_status_example_3

Comment 3 Yaacov Zamir 2021-11-01 13:15:10 UTC
This looks bad, but it has limited loss of functionality and limited impact to the customer's functionality.

setting to blocker(-) leaving as severity high

Comment 4 Gilad Lekner 2021-12-29 09:00:28 UTC
@gouyang I can't understand the 2nd and 3rd screenshots, they are very low quality

regarding the first one with the Migrating status, can you please try to check again?
I believe one of my recent PRs may have fixed this issue.
The backend printableStatus has a Migrating status, so if its not Migrating in the YAML and in the details page it is Migrating, maybe the details page status is wrong.

Comment 5 Guohua Ouyang 2022-01-04 04:22:20 UTC
(In reply to Gilad Lekner from comment #4)
> @gouyang I can't understand the 2nd and 3rd screenshots, they are
> very low quality
I used the wrong file type while recording, it should be gif. Sorry about that.

> 
> regarding the first one with the Migrating status, can you please try to
> check again?
> I believe one of my recent PRs may have fixed this issue.
> The backend printableStatus has a Migrating status, so if its not Migrating
> in the YAML and in the details page it is Migrating, maybe the details page
> status is wrong.

Checked on the latest console, the problem is still existing while migrating VM.
On overview page, the status becomes "migrating" immediately, but on VM list page, it's "Running". (it becomes migrating for a short time after some time).

It seems it uses different ways to show status on List page/Overview page/Details page.

Comment 8 Guohua Ouyang 2022-01-27 09:34:55 UTC
It improved status on list view page and overview page.
But VM details page is still different from overview page and list view page.

Comment 14 errata-xmlrpc 2022-08-10 10:38:21 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 (Important: OpenShift Container Platform 4.11.0 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.

https://access.redhat.com/errata/RHSA-2022:5069


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