Bug 1166307 - Content search: content view compare seems to hang indefinitely and/or eventually not respond to click
Summary: Content search: content view compare seems to hang indefinitely and/or eventu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Corey Welton
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1201937 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-20 19:16 UTC by Corey Welton
Modified: 2019-10-10 09:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:19:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Corey Welton 2014-11-20 19:16:21 UTC
Description of problem:
Trying to compare content views sometimes doesn't seem to return any results (spinner of death).  Eventually, clicking the compare button no longer does anything.

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


How reproducible:


Steps to Reproduce:
1.  Create environments
2.  Create/sync/promote a few repos called ('rhel65_i386', 'rhel65_x86_64'), etc., into content views named the same.
3.  Go to content search
4.  Select content views from dropdown and enter 'rhel' into the searchbox; add.
5.  Submit to see results.
6.  Within results, select 2 or more items and hit 'Compare'.

Actual results:
Spinner for a long time, no results.
It also appears that sometimes, when trying subsequent comparisons, clicking the Compare button does nothing.

Expected results:
Proper comparisons.

Additional info:

Comment 2 Eric Helms 2015-02-27 21:33:19 UTC
Created redmine issue http://projects.theforeman.org/issues/9586 from this bug

Comment 3 Bryan Kearney 2015-03-11 16:04:26 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9586 has been closed
-------------
Eric Helms
Applied in changeset commit:katello|973918eeb03fe3db1c1b6ab643977d57c1bdab97.

Comment 4 Tom McKay 2015-03-15 15:39:00 UTC
*** Bug 1201937 has been marked as a duplicate of this bug. ***

Comment 7 Corey Welton 2015-03-27 02:49:53 UTC
I can verify this; that said, the help bubble that appears remains messed up and I had some problems actually clicking the button, which seems sort of finicky.  But it does work, the root issue is resolved.  Bugs can be written for the other thing.

Verified in Satellite-6.1.0-RHEL-7-20150324.0

Comment 8 Dave Sullivan 2015-05-28 14:59:34 UTC
I see this is verified for Satellite 6.1  RHEL7, what about Satellite6.1 RHEL6?

Comment 9 Eric Helms 2015-06-08 12:49:00 UTC
Yes, this is verified for RHEL6 as well.

Comment 10 Bryan Kearney 2015-08-11 13:27:25 UTC
This bug is slated to be released with Satellite 6.1.

Comment 11 errata-xmlrpc 2015-08-12 05:19:44 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/RHSA-2015:1592

Comment 12 Dave Sullivan 2015-08-17 13:23:00 UTC
Comment #7 bothers me a little bit, already got this message back from customer

"I am not able to click on "Compare Selected" i am using firefox 31.8.0"

Are we documenting browser versions tested/supported?

Comment 13 Dave Sullivan 2015-08-17 13:28:34 UTC
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Prerequisites.html#form-Red_Hat_Satellite-Installation_Guide-Prerequisites-Supported_Browsers

Ok, so I don't think saying the "latest" helps that much.

As we don't really know what that means, latest yesterday, 2 weeks ago, latest today, or three weeks into the future.

We probably should update the doc on the lastest version tested and provide an actual version.


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