Red Hat Bugzilla – Bug 1313846
selecting the Oscap_Proxy throws TypeError as seen from Firebug
Last modified: 2016-07-27 07:18:25 EDT
Description of problem:
selecting the Oscap_Proxy host throws TypeError as seen from Firebug
Firebug shows the below error when selecting "Openscap proxy":
TypeError: $(...).indicator_show is not a function
No issues seen in "/var/log/foreman/production.log"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure OSCAP plugin and restart services
2. create a "New Host" and specify the "oscap proxy" to note the above TypeError in FireBug.
Issues seen with selecting the "oscap proxy"
Firebug should throw no issues while selecting the "oscap proxy".
These issue are seen both in FF and chrome.
POST https://abc.redhat.com/hosts/openscap_proxy_changed 404 (Not Found)send @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:27st.extend.ajax @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:27updateOpenscapProxy @ openscap_proxy-3b847fe7ed27cdc7b6678b9fb3775af368520aa8615c6f83b5958e761dc3f857.js:1onchange @ new:371st.event.trigger @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:26(anonymous function) @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:26st.extend.each @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:15st.fn.st.each @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:15st.fn.extend.trigger @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:26E.triggerChange @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:604E.onSelect @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:605E.selectHighlighted @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:604(anonymous function) @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:604(anonymous function) @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:604st.event.dispatch @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:26g.handle @ application-8c003690572a3ba05aa2be14d1d396a74808b692604127df092aa9c2ae46f324.js:25
I think this is more easily reproducible if we have 2 OSCAP proxies and not just one to choose from.
Created redmine issue http://projects.theforeman.org/issues/14561 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/14561 has been closed
*** Bug 1337868 has been marked as a duplicate of this bug. ***
Build : satellite 6.2 Snap 16.0
Verified , no TypeError while selecting OSCAP proxy
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.