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.
Description of problem:
When creating AKs, user will sporadically get a "Loading...." hang, upon submission. This is apparently due to a resource 404. This 404, in turn, is due to things being completed/returned too quickly for elasticsearch, which is apparently returning our ak info.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150317.0
How reproducible:
Sometimes!! It seems to happen every 2-3 AK creates on this box, but not every time. On jcalla's box, we haven't seen it at all.... yet.
Steps to Reproduce:
1. attempt to create an activation key; submit.
2. If you do not get stuck, repeat step 1 until you do get stuck
3. View results
Actual results:
* UI reading "Loading...." with a misplaced "environments" arrowhead
* Console in chrome reads
Remote Address:10.16.4.115:443
Request URL:https://rhsm-qe-3.rhq.lab.eng.bos.redhat.com/katello/api/v2/activation_keys/15?fields=full
Request Method:GET
Status Code:404 Not Found
* In production log:
2015-03-23 14:44:49 [I] Completed 404 Not Found in 18ms (Views: 0.3ms | ActiveRecord: 0.9ms)
2015-03-23 14:44:50 [I] Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.2.0.26/app/views/katello/api/v2/environments/paths.json.rabl within katello/api/v2/layouts/collection (225.3ms)
Expected results:
No 404s, "Loading" page 'just works.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9887 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|a15d5098b0252eaeed3bc4a8c59ede2177f61593.
I don't see the change from this bug to be present in the recent satellite 6 builds and I was able to reproduce the issue. Probably cherry-pick missed in the process
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-2015:1911