Bug 1648340

Summary: satellite UI stops responding when viewing running task on Tasks page
Product: Red Hat Satellite Reporter: Jameer Pathan <jpathan>
Component: Tasks PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Jameer Pathan <jpathan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: aruzicka, inecas, jhutar, nkathole
Target Milestone: Unspecified   
Target Release: Unused   
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: 2018-11-13 17:03:43 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:
Attachments:
Description Flags
scrrenshot1
none
screenshot2
none
screenshot3 none

Description Jameer Pathan 2018-11-09 13:11:37 UTC 
Description of problem:
satellite UI stops responding when viewing running task on Tasks page

Version-Release number of selected component (if applicable):
@satellite 6.5.0 snap 2

How reproducible:
always

Steps to Reproduce:
1. go to Monitor > Tasks
2. click on task which is in running state
3. wait few seconds, everything except content related to
Tasks page starts disappearing.

Actual results:
everything except content related to
Tasks page starts disappearing.

Expected results:
page should remain as it is when seeing for first time.

Additional info:
slows down the browser.
Comment 1 Jameer Pathan 2018-11-09 13:19:30 UTC 
Created attachment 1503644 [details]
scrrenshot1
Comment 2 Jameer Pathan 2018-11-09 13:20:01 UTC 
Created attachment 1503645 [details]
screenshot2
Comment 3 Jameer Pathan 2018-11-09 13:20:30 UTC 
Created attachment 1503646 [details]
screenshot3
Comment 5 Brad Buckingham 2018-11-13 17:03:43 UTC 

*** This bug has been marked as a duplicate of bug 1647799 ***
Comment 6 Adam Ruzicka 2018-11-26 07:45:51 UTC 
*** Bug 1653038 has been marked as a duplicate of this bug. ***