Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1337868 - selecting oscap proxy from host-group form shows 404 not found
Summary: selecting oscap proxy from host-group form shows 404 not found
Keywords:
Status: CLOSED DUPLICATE of bug 1313846
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Shlomi Zadok
QA Contact:
URL:
Whiteboard:
Depends On: 1313846
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-20 09:56 UTC by Kedar Bidarkar
Modified: 2019-06-13 21:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-23 12:36:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kedar Bidarkar 2016-05-20 09:56:24 UTC 
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:
Comment 3 Shlomi Zadok 2016-05-23 03:52:55 UTC 
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
Comment 4 Brad Buckingham 2016-05-23 12:34:16 UTC 
Thanks Shlomi!  Updating the bz to align to same release as bug 1313846.
Comment 5 Kedar Bidarkar 2016-05-23 12:36:49 UTC 

*** This bug has been marked as a duplicate of bug 1313846 ***
Note You need to log in before you can comment on or make changes to this bug.