Red Hat Bugzilla – Bug 433676
Cannot Delete mutiple System Profiles. Results in a 404 Error
Last modified: 2009-03-26 16:50:21 EDT
Description of problem:
When selecting multiple systems, clicking Manage on the top right, then trying
to remove these systems the result is a 404 Page Not Found Error and the systems
are not removed.
Version-Release number of selected component (if applicable):
Red Hat Network release 5.0.4
Steps to Reproduce:
2. Click Systems
3. Select systems you'd like to delete
4. Click Next (>) so that the grey bar notices the amount of systems you select
(This is broken as well that will be in another bug).
5. Click Manage on the upper right
6. Click Misc or use the link on the Overview page to delete systems
7. Confirm your deletion
Get a 404 Error
I could not reproduce the problem.
I tried on both rhn.redhat.com and rhn.webqa.redhat.com (login as org admin),
and I was able to delete three system profiles without error. I also tried
login as a normal user, and it worked too.
In trying to delete 95 systems the error is very reproducible. It takes quite
some time to actually delete systems.
The URL at the time was:
After clicking "Confirm Deletions" the URL is the same and the 404 Error is there.
"It takes quite some time to actually delete systems."
"It take quite some time in attempting to delete the systems."
Successful deletions with number of systems selected via WEB UI:
Unsuccessful deletions with number of systems selected via WEB UI:
When trying to delete the systems there were 5 systems on the first page that
could not be selected. Thus this allowed for only 45 of the total 50 systems to
be selected for deletion. When deleting > 50 systems this included the 45 on the
first page and a selection of boxes on the second page.
Also when trying to delete 50 systems a 500 Internal Server Error popped up. I
am still investigating.
Re: 500 Internal Server Error
This occurred but the systems were deleted.
I've also tried with the last 83 systems. The result is the same as the attempt
to delete 95 systems. I'll hold off testing since these are the last 83 systems
and I'd like to keep a reproducible case hanging around for further investigation.
Could not reproduce it either on 5.0.5 production or on 5.0.6 stage. I have
successfully deleted a system set containing 45, 50, 85 and 105 servers.
This bug should have been marked as closed per SSkracic: UPDATE (Seb 2008-06-19): could not reproduce it, so marked as CLOSED/CURRENT_RELEASE.