Bug 1870634

Summary: Topology Filtering Off and On Application Groups Has a Slow Reaction Time
Product: OpenShift Container Platform Reporter: Jeff Phillips <jephilli>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Jaivardhan Kumar <jakumar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: aballant, aos-bugs, jakumar, nmukherj
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.6.0-0.nightly-2020-08-18-165040 Cluster ID: f844bc36-a328-4dd9-adab-842f0051a000 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.135 Safari/537.36
Last Closed: 2020-10-27 16:30:13 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:

Description Jeff Phillips 2020-08-20 13:44:57 UTC
Description of problem:

When filtering out resources that are all in the same application group, the group disappears with the nodes. If you re-enable them back, the group sometimes takes a moment to re-render and thus the nodes are separate.

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

How reproducible:


Steps to Reproduce:

1. Add a couple Deployments to the same group
2. Add another resource type
3. Filter to the other resource type (thus removing the Deployments)
4. Then remove the filters

Actual results:

The deployments were grouped, hidden, then ungrouped for a short period of time before the group re-renders around the deployments.

Expected results:

The group to immediately return when the deployments do

Additional info:

Comment 4 Jaivardhan Kumar 2020-08-26 09:55:26 UTC
Verified onĀ 4.6.0-0.nightly-2020-08-26-032807

Comment 6 errata-xmlrpc 2020-10-27 16:30:13 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.