Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionOleksandr Shtaier
2016-03-24 14:48:41 UTC
Description of problem:
Like stated in title we have an issue with Content View field for Host entity. Mainly that affects test automation as you will never be able to create new Host entity as CV is required field. Of course, it will be nice to use some workarounds in the script itself, but waiting logic is most fundamental level and it is really bad idea to change it.
Also, it can affect not only test automation, but impact application itself in more or less serious way
Version-Release number of selected component (if applicable):
6.2 SNAP5
How reproducible:
Always
Steps to Reproduce:
1. Go to New Host window (Hosts->New Host)
2. Specify Organization and Location
3. Select Lifecycle Environment (Library)
4. 404 error returned for 'spinner.gif' resource (just annoying thing, I doubt that it has any impact)
5. Select Content View (Default Organization View)
Actual results:
Necessary content view is selected and jQuery.active=1
Expected results:
Necessary content view is selected and jQuery.active=0
Additional info:
Comment 1Oleksandr Shtaier
2016-03-24 14:49:22 UTC
Oleks,
I am not sure exactly what to test for jQuery.active. Is that a response for some ajax call?. I believe a bug related to lifecycle environment and content view was fixed in the recent snap. Can ya retest this part and fail if it still occurs
(In reply to Partha Aji from comment #5)
> Oleks,
> I am not sure exactly what to test for jQuery.active. Is that a response
> for some ajax call?. I believe a bug related to lifecycle environment and
> content view was fixed in the recent snap. Can ya retest this part and fail
> if it still occurs
Partha,
jquery.active is a jquery function signaling whether there are any ajax calls pending. Our automation is based on selenium webdriver, which relies on output of this function as it typically waits until all the ajax calls are finished before checking for a presence of some element, etc.
you can call the .active function yourself by calling
$.active
from a browser javascript console.
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/RHBA-2016:1501