Bug 587745 - Deleting a large number of system profiles results in 500 Error
Summary: Deleting a large number of system profiles results in 500 Error
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 530
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Red Hat Satellite QA List
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
Reported: 2010-04-30 19:00 UTC by Stephen Benjamin
Modified: 2010-07-13 03:13 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-07-13 03:13:53 UTC

Attachments (Terms of Use)

Description Stephen Benjamin 2010-04-30 19:00:16 UTC
Description of problem:
Deleting a large number of systems profiles from Satellite results in a 500 error.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attempt to delete 180+ servers profiles from Satellite
2. Wait 10+ minutes
3. Fail!
Actual results:
500 Internal Server Error

Expected results:

Additional info:
Works for smaller amounts of servers

Comment 1 Clifford Perry 2010-05-12 14:07:45 UTC
Hi  Stephen Benjamin, 
This bug report does not contain much detail to work with currently. 

Could you please open a support ticket to associate and track next to this bug
report. This will allow for Red Hat support to triage, confirm replication and
help Engineering - sometimes providing a fix before we even start looking at
the bug report. 


Comment 2 Stephen Benjamin 2010-05-12 14:13:56 UTC
Unfortunately I can't go into our Satellite server and try this again, as we've already deleted the servers we wanted to.  But I'm not sure what detail you would require.  If you login to Satellite, and attempt to remove 180 or more (it may be less, I didn't test) server profiles, satellite responds with a 500 Internal Server Error.

Comment 3 Clifford Perry 2010-05-12 14:26:23 UTC
The starting point for *any* troubleshooting is getting the exact traceback error message (from server logs - ISE 500 is next to useless besides telling us something went wrong). We then can use that to ensure any replication confirms replication of not only symptoms, but also error. We then look to address the error by determining what caused the error message (the traceback generating the ISE 500) and then being able to confirm for our customers and users that we have fixed their specific bug. Without proper troubleshooting and gathering of data we risk fixing the wrong issue. We may also discover that we cannot replicate your issue due to some environment issue at play. 

As such, please, follow my advise given previously so that we can correctly troubleshoot this through our support organization. 


Note You need to log in before you can comment on or make changes to this bug.