Bug 859522 - Systems > Subscriptions > Available Subscriptions dropdown begins incessantly flickering upon page load
Summary: Systems > Subscriptions > Available Subscriptions dropdown begins incessantly...
Keywords:
Status: CLOSED DUPLICATE of bug 859038
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Jason E. Rist
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-21 18:03 UTC by Corey Welton
Modified: 2013-08-16 17:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-21 18:23:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Corey Welton 2012-09-21 18:03:20 UTC
Description of problem:
When user loads the referenced page, the dropdown for "Available Subscriptions" flickers on and off at random, apparently until user clicks somewhere in the page or something.

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


How reproducible:
Seems everytime, with Firefox and Chrome

Steps to Reproduce:
1.  Subscribe and sync some RHEL channels.
2.  Register a system to CFSE -- you might want to use an activation key (that's what was done here)
3.  Navigate to Systems > All > $system > Subscriptions
4.  View results  

Actual results:
The dropdown for "Available Subscriptions" goes crazy.

Expected results:
Normal UI.

Additional info:

 CloudForms System Engine Version: 1.1.12-7.el6cf

Comment 1 Corey Welton 2012-09-21 18:04:25 UTC
I dunno if it is a blocker, but it is surely extremely annoying/jarring.  I also am not sure, offhand, if it results in other effects elsewhere in the product.

Comment 2 Tom McKay 2012-09-21 18:23:49 UTC

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

Comment 3 Mike McCune 2013-08-16 17:54:54 UTC
getting rid of 6.0.0 version since that doesn't exist


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