Bug 1804730 - Remove the Monitoring Decorator in Topology
Summary: Remove the Monitoring Decorator in Topology
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Vikram Raj
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1804727
TreeView+ depends on / blocked
 
Reported: 2020-02-19 14:18 UTC by Vikram Raj
Modified: 2020-07-13 17:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:16:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4366 0 None closed Bug 1804730: Remove monitoring warning decorator 2020-06-23 08:37:30 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:16:36 UTC

Description Vikram Raj 2020-02-19 14:18:44 UTC
Description of problem:
Since warnings stick around, this mechanism is misleading. In 4.5, with Alerts, we can bring this decorator back, only exposing Alerts.

Remove the decorator in the top left quadrant for 4.4

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


How reproducible:


Steps to Reproduce:
1. Add a project by selecting the wrong builder image. 
2. In the topology view, you will see the decorator in the top left quadrant of the workload.

Actual results:
Decorator is visible the decorator in the top left quadrant for 4.4

Expected results:
Decorator should not be visible

Comment 3 Gajanan More 2020-03-06 07:12:34 UTC
I have validated this bug on:
Build: 4.5.0-0.ci-2020-03-05-232742
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.

Comment 5 errata-xmlrpc 2020-07-13 17:16:11 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, 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:2409


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