Bug 2078709 - VM conditions column have wrong key/values
Summary: VM conditions column have wrong key/values
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-26 05:14 UTC by Guohua Ouyang
Modified: 2023-11-13 08:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:31:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-17827 0 None None None 2023-11-13 08:19:41 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:31:34 UTC

Description Guohua Ouyang 2022-04-26 05:14:00 UTC 
Description of problem:
VM conditions column have wrong key/values, it seems is the combination of the 'reason' and 'status' in '.status.conditions'.
eg: 
VMINotExists=False  while vm is stopped
DisksNotLiveMigratable=False while VM disk is using HPP


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

How reproducible:


Steps to Reproduce:
1. create a VM and check VM conditions in list view
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Guohua Ouyang 2022-05-19 02:25:13 UTC 
verified on v4.11.0-369
Comment 4 errata-xmlrpc 2022-09-14 19:31:19 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 Virtualization 4.11.0 Images security and bug fix 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:6526
Note You need to log in before you can comment on or make changes to this bug.