Red Hat Bugzilla – Bug 855278
I'm getting jQuery error when adding command includes "??" into the sudo commands field in IPA web interface.
Last modified: 2013-03-07 19:13:25 EST
Created attachment 610651 [details] Video showing the bug. *** Description of problem: I can't add the following command into sudo command list: echo "??" > /tmp/test *** Version-Release number of selected component (if applicable): ipa-server-2.2.0-16.el6.x86_64 *** How reproducible: See the steps below *** Steps to Reproduce: 1. Go to IPA WEB-GUI 2. Select Policy -> Sudo -> Sudo commands -> Add 3. Add sudo command: echo "??" > /tmp/test 4. Click add *** Actual results: Currently I'm getting error "jQuery15208158273949015573_1346241267446 was not called". *** Expected results: The command should be saved without any error. *** Additional info: I can see the other IPA forms has also problems with "??" (like adding sudo rules).
Hello. I can add the command through command line: # ipa sudocmd-add "echo '??' > /tmp/test" ------------------------------------------ Added Sudo Command "echo '??' > /tmp/test" ------------------------------------------ Sudo Command: echo '??' > /tmp/test -> but the web gui is still showing the jQuery error. Regards PetrR
This is an error of bundled jquery library in IPA 2.2. Upstream version: FreeIPA 3.0 contains newer version so there isn't this problem. Updating to jquery-1-7-1.js fixes this problem but it introduces another in sshkey_widget so setting of ssh public keys stop working.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/3073
This is not a valid bug for 6.4, but proposing as hotfix for 6.3
Fixed upstream. ipa-2-2: 08e3fbb3b6c1c043feda6d72e50a8d35c482098c
verified using ipa-server-3.0.0-22.el6.x86_64 Now we can add the following command into sudo command list:echo "??" > /tmp/test 1. Go to IPA WEB-GUI 2. Select Policy -> Sudo -> Sudo commands -> Add 3. Add sudo command: echo "??" > /tmp/test 4. Click add
Created attachment 689144 [details] jQuery error fixed
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. http://rhn.redhat.com/errata/RHSA-2013-0528.html