Description of problem: We see this issue for both firefox and chrome browsers, while selecting the OSCAP proxy from both host-group and hosts. POST https://oscap.redhat.com/hostgroups/openscap_proxy_changed 404 (Not Found)send @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:27st.extend.ajax @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:27updateOpenscapProxy @ openscap_proxy-3b847fe7ed27cdc7b6678b9fb3775af368520aa8615c6f83b5958e761dc3f857.js:1onchange @ new:332st.event.trigger @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:26(anonymous function) @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:26st.extend.each @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:15st.fn.st.each @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:15st.fn.extend.trigger @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:26E.triggerChange @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:604E.onSelect @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:605E.selectHighlighted @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:604(anonymous function) @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:604(anonymous function) @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:604st.event.dispatch @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:26g.handle @ application-3c4768bf2dcc5be221d91702179e80d17b33f0c1940ebbf5d423814824814745.js:25 Version-Release number of selected component (if applicable): TESTED with sat6.2-snap12.1 How reproducible: Steps to Reproduce: 1. select the oscap proxy in host-group or hosts page 2. 3. Actual results: Turns the select box red and chrome shows 404 not found message Expected results: Selecting the oscap proxy should be clean. Additional info:
Brad, I believe it is solved with https://github.com/theforeman/foreman_openscap/pull/162 -- this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1313846
Thanks Shlomi! Updating the bz to align to same release as bug 1313846.
*** This bug has been marked as a duplicate of bug 1313846 ***