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

Bug 1804994

Summary: incorrect border for groups matching filter in topology
Product: OpenShift Container Platform Reporter: cvogt
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, nmukherj, rgarg
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1804991 Environment:
Last Closed: 2020-05-13 21:59:29 UTC Type: ---
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: 1804991    
Bug Blocks:    

Description cvogt 2020-02-20 03:40:04 UTC 
+++ This bug was initially created as a clone of Bug #1804991 +++

Description of problem:
Knative service, helm group, and operator backed groups have a dashed border. Even when the node name matches the filter, the dashed border remained and changed to orange.

According to the designs, the border should be solid when matching the filter text.

How reproducible:


Steps to Reproduce:
1. deploy a knative service to your namespace
2. go to developer console -> topology
3. enter filter text in the top right input field

Actual results:
Border of knative service is a dashed orange line.


Expected results:
Border of knative service is a solid orange line.
Comment 3 Ruchir Garg 2020-03-02 06:38:35 UTC 
Bulk assigning all to Gajanan for verification.
Comment 4 Gajanan More 2020-03-03 09:20:19 UTC 
Gajanan More has validated the bug (ODC-3076) on
Build: 4.4.0-0.ci-2020-03-03-033811
Browser: Google Chrome Version 78.0.3904.108
Comment 6 errata-xmlrpc 2020-05-13 21:59:29 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:0581