Description of problem: New SCAP content cannot be created in Satellite and fails with error " Oops, we're sorry but something went wrong 500 Internal Server Error" Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch How reproducible: Always Steps to Reproduce: 1. Navigate to Satellite WebUI -> Hosts -> SCAP contents. Click on 'New SCAP Content'. 2. Enter any Title. Browse a SCAP Datastream .xml file. Assign required Organizations and Locations. 3. Click on Submit. Actual results: The web page loads for a while and then throws following error: "Oops, we're sorry but something went wrong 500 Internal Server Error" Expected results: The new SCAP content should get created successfully. Additional info: Attaching screen image of observed error in the BugZilla.
Created attachment 1942760 [details] Observer Error
When you see 500 error, always please attach the production.log. Or at least the foreman-rake output that is mentioned on that 500 error page. In this case, we may also need to capture the proxy.log from Capsule that was appended during the scap content parsing.
The requested logs has been attached to the case. Please refer attachments. I have kept the attachments private since it contain hostnames and other confidential host information. Please let me know if any more inputs needed from my end.
Is this a regression from 6.12? Thanks!
This issue is present in Satellite 6.12 also!
So, the proxy log says "2023-02-09T16:09:33 9ad5a98c [W] Error details for Error occurred: Failed to parse profiles: <Exception>: Error occurred: Failed to parse profiles". I have a suspicion that the file is not valid. I think we've seen something like this before. Can you upload your DS file here for further investigation please?
Hello Marek, You are right. I tried with another right DS file and the upload was successful. So the mentioned error is observed only when the DS file being uploaded is not valid. I believe if the DS file which is being uploaded is not valid, Satellite should throw some meaningful error or warning instead of 500 Internal Server Error.
Hi Jayant, Based upon the finding that the uploaded file isn't valid, should we close this one as notabug or duplicate of bug 2168728? Thanks!
Hello Brad, The same issue is observed while creating new scap content and while creating new tailoring file if invalid DS file is used. Are we are going to fix both scenarios (scap content and tailoring file) in BZ-2168728? If yes, then we can close out this BZ.
Well, I believe the issue is exactly the same as what was reported in https://bugzilla.redhat.com/show_bug.cgi?id=2133151 And if i use the DS file from https://access.redhat.com/security/data/metrics/ds/com.redhat.rhsa-RHEL7.ds.xml , I can reproduce the 500 ISE as expected in Sat 6.13 as well. It does not fails with the error "Scap file Invalid XML format" but instead i get the same 500 ISET as that BZ and this BZ.
Closing this BZ as it is a duplicate of the existing reported earlier https://bugzilla.redhat.com/show_bug.cgi?id=2133151 *** This bug has been marked as a duplicate of bug 2133151 ***