Description of problem: 4/14 rhel 4 server recreate: 1. sync rhel 4 / 5 channels 2. errata -> managed 3. select all 4. delete selected errata ( which could be about 1500 items) get We're sorry, but the erratum could not be found. This error may have occurred in one of three ways: 1. The erratum requested does not exist. This is most likely if you arrived at this page through bookmarks or some other non-hyperlink. 2. You do not have permission to view this erratum. 3. You've found an error in our site. Please help us by filling out this form with details of how you received this message.
Following the instructions, Cliff and I cannot reproduce. Please reopen with additional information if you can still reproduce it.
I would certainly disagree ;) recreate: 1. sync rhel 4 / 5 channels 2. errata -> managed 3. select all 4. delete selected errata ( which could be about 1500 items) 4/20 build after twenty minutes, never returns java process > 100% looking at top.
Comment #2 says that the procedure doesn't return, but the summary of this bug is about a 404, which we never saw. If the issue is the not returning, please modify the summary to match what you are seeing.
on rhel 4, 4/14 build the transaction would finish and load the wrong page at the end. The page load was an errata not found page. on rhel5 on 4/20 the transaction never completes
Since unable to reproduce the 404 but the never completes. Approved. Possible dupe of bug 497458 Cliff
d7b4797 Deleting about 1500 errata should take about 25 seconds now, vs 10-20 minutes we were seeing before. I modified everything to use bulk queries instead of queries for each errata. So instead of running 6 queries 1500 times, it just runs them once.
verified 5/21.1
Release Pending Deleting all managed errata completed on test1182.test.redhat.com
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html