Red Hat Bugzilla – Bug 1123519
JavaScript syntax error when displaying hosts for organization: Error: Syntax error, unrecognized expression: %22Default_Organization%22'
Last modified: 2017-02-23 16:10:25 EST
Description of problem: There is a JavaScript syntax error when displaying hosts for organization: "Error: Syntax error, unrecognized expression: %22Default_Organization%22'" Version-Release number of selected component (if applicable): Satellite-6.0.4-RHEL-6-20140723.0 How reproducible: always Steps to Reproduce: 1. In webUI go to: Administration -> Organizations -> click number in column "Hosts" ("0" in my case) on row with "Default_Organization" 2. On the page which loads, watch Firefox console for JavaScript error Actual results: Error: Syntax error, unrecognized expression: %22Default_Organization%22' application-3445874bf5e8cab38af5fa7b69530376.js:18 Expected results: No syntax errors Additional info: Not sure if this is Katello or Foreman issue
Same for .../localtions and possibly others places as well.
I can't reproduce this, could you provide the full URL from your browser please?
Created redmine issue http://projects.theforeman.org/issues/6797 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/6797 has been closed ------------- Tomer Brisker Could not reproduce in current dev branch. Looks like this was resolved by a previous commit. Resolving, please re-open and provide more details if this still occurs.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** foreman-release-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-gce-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el6.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-proxy-1.0-1.noarch foreman-postgresql-1.7.0-0.develop.201410150839gitb948163.el6.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-broker-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-qpid-client-cert-1.0-1.noarch foreman-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-ovirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch foreman-vmware-1.7.0-0.develop.201410150839gitb948163.el6.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6.noarch ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el6.noarch rubygem-hammer_cli_foreman-0.1.3-1.201410151235gitbc8c449.el6.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el6.noarch foreman-proxy-1.7.0-0.develop.201410101404git7961640.el6.noarch qe-foreman-rhel65.usersys.redhat.com-puppet-client-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-foreman-client-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-apache-1.0-1.noarch qe-foreman-rhel65.usersys.redhat.com-parent-cert-1.0-1.noarch foreman-compute-1.7.0-0.develop.201410150839gitb948163.el6.noarch ruby193-rubygem-foreman-tasks-0.6.10-1.el6.noarch foreman-libvirt-1.7.0-0.develop.201410150839gitb948163.el6.noarch
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592