Bug 1425800 - Host Collection still working *never conclude* when checking the Errata tab
Summary: Host Collection still working *never conclude* when checking the Errata tab
Keywords:
Status: CLOSED DUPLICATE of bug 1417642
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.7
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-22 13:08 UTC by Waldirio M Pinheiro
Modified: 2020-12-14 08:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 00:50:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Waldirio M Pinheiro 2017-02-22 13:08:37 UTC
Description of problem:
So customer have one Host Collection with ~ 400 content hosts, all of them RHEL7, when customer click on Errata tab just to see all erratas available to all 400 content hosts the spin still forever, if customer keep the session alive, working with another session, he told me, one time was possible to see the result after 30 minutes, btw when doing any filter, stopped work, then was necessary redo the steps and the same behavior.

I create one Host Collection with 2 content hosts, worked as expected, faster.

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

How reproducible:
100% on customer environment *with 400 content hosts*

Steps to Reproduce:
1. Create one Host Collection
2. Add 400 content hosts
3. Click on Host Collections - Errata Tab

Actual results:
spin still working forever

Expected results:
See all erratas available to all content hosts

Additional info:

Comment 3 Ivan Necas 2017-02-22 13:24:52 UTC
Should we close this bz as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1417642 then?

Comment 5 Pradeep Kumar Surisetty 2017-02-23 00:50:27 UTC

*** This bug has been marked as a duplicate of bug 1417642 ***


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