cumin-0.1.3109-1.el5.noarch on a RHEL5.3 box Trying to modify the attributes of a running grid job with "Edit Attributes", I notice that the Submit and Cancel buttons don't leave the page. The attributes are changed as expected, so this is just a minor annoyance. These appear in the Error Console (Firefox 3.0.6 on F10) Warning: variable elems redeclares argument Source File: http://<mynode>:45672/resource?name=wooly.js Line: 120, Column: 20 Source Code: var elems = elem.getElementsByTagName(child); Warning: variable node redeclares argument Source File: http://<mynode>:45672/resource?name=wooly.js Line: 147, Column: 12 Source Code: var node = result.iterateNext(); Warning: anonymous function does not always return a value Source File: http://<mynode>:45672/resource?name=wooly.js Line: 313, Column: 12 Source Code: }
*** Bug 476811 has been marked as a duplicate of this bug. ***
Fixed (I hope) in cumin 3130. It appears that different OS releases handle the http header REFERRER differently. Submit and Cancel should now return to the View job Ads page.
Still does not work for me in cumin-0.1.3120-1.el5 Strangely enough, it works for completed or removed job, but not when viewing properties of a running one. FYI, accessing properties (clicking on job ID) of any completed/removed job is noticably slower compared to doing the same for running/idle job.
Please try with cumin version 3130. That is the version I made the changes in.
On cumin-0.1.3137-1.el5 I am getting APPLICATION ERROR after clicking on any of "Submit" or "Cancel". When I run Cumin on a console with cumin --debug --addr 192.168.1.8 --log-level debug I am unable to find there any sensible output regarding the error.
Fixed the APPLICATION ERROR in cumin version 3141.
Please build a new cumin package so I can test it. Thanks.
Working as expected on cumin-0.1.3160-1.el5 Thanks!
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0434.html