Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1879059

Summary: Ensure that VM or VMI specific alerts are shown prominently in the UI
Product: OpenShift Container Platform Reporter: Fabian Deutsch <fdeutsch>
Component: Console Kubevirt PluginAssignee: Yaacov Zamir <yzamir>
Status: CLOSED WONTFIX QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, cnv-qe-bugs, ncredi, tnisan, ycui, yzamir
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-10 11:29:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1860671    
Bug Blocks:    

Description Fabian Deutsch 2020-09-15 11:02:05 UTC
Description of problem:
There can be VM and VMI specific alerts (prometheus alerts) that should be displayed prominently in the ui.
It has to be decided if in the VM details, or elsewhere

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

How reproducible:


Steps to Reproduce:
1. Create a VM, watch the VM for alerts (not events)
2.
3.

Actual results:
Alerts appear in the cluster monitoring section

Expected results:
Alerts should appear in the VM specific section

Additional info:
I'm not sure if we have VM/VMI specific alerts today!

Comment 3 Tomas Jelinek 2020-09-24 05:40:25 UTC
This is not a 4.6 blocker, moving to 4.7 to not to block the release

Comment 4 Tal Nisan 2021-05-10 11:29:03 UTC
Will be fixed as a part of https://issues.redhat.com/browse/CNV-11297, closing the bug as the more thorough tracking of the feature will be done in the Jira issue, can't find a more fitting resolution than WONTFIX though, the new redesign of the status will solve this issue.