Red Hat Bugzilla – Bug 1204929
activation key - create: "Loading...." hangs on UI due to 404/elasticsearch error
Last modified: 2017-02-23 15:15:44 EST
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:
FWIW, according to jsherrill, this is a bz no matter what because elasticsearch shouldn't be used to return such sorts of results anymore, anyway.
Created redmine issue http://projects.theforeman.org/issues/9887 from this bug
PR: https://github.com/Katello/katello/pull/5135
Moving to POST since upstream bug http://projects.theforeman.org/issues/9887 has been closed ------------- Walden Raines Applied in changeset commit:katello|a15d5098b0252eaeed3bc4a8c59ede2177f61593.
Verified by QE on version Satellite-6.1.0-RHEL-7-20150324.0
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
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
*** Bug 1252150 has been marked as a duplicate of this bug. ***
cherry-picked commit a15d5098b0252eaeed3bc4a8c59ede2177f61593
Verified in 6.1.3 compose #2
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