Bug 469051 - Cloning errata is very slow
Cloning errata is very slow
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Clifford Perry
Red Hat Satellite QA List
: Triaged
Depends On:
Blocks: 462714 479461
  Show dependency treegraph
Reported: 2008-10-29 13:40 EDT by Anthony Green
Modified: 2014-05-09 06:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-09 06:20:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anthony Green 2008-10-29 13:40:11 EDT
Description of problem:
Cloning errata is very very slow.

From IRC:
(09:48:37 AM) mike: green: heh, its taking a long time in a method called:
(09:48:43 AM) mike: cloneErrataFast()
(09:49:06 AM) mike: green: yeah, something isnt right with this, taking way too long.

Version-Release number of selected component (if applicable):
I found this on 5.1.1.  I haven't tested any other release.

How reproducible:

Steps to Reproduce:
1.Clone the 32-bit x86 RHEL 5 channel with 0 errata
2.Clone all of the 600+ errata into the cloned channel
Actual results:
It works, but takes between 30 and 90 minutes (I left my computer at 30min when it was still working.  It was finished when I returned at 90min).

Expected results:

Additional info:
Comment 1 Mike McCune 2008-10-29 13:42:37 EDT
I saw this as well.  It took over 60 minutes on rlx-1-16 to clone 600 errata.
Comment 7 Clifford Perry 2014-05-09 06:20:56 EDT
We have not addressed this specific bug for over 4 years. This bug was reported as either Satellite 5.0 or 5.1, both of which have now End of Life and not supported. I am closing out as wontfix to clear from backlog. 

Please re-open if you disagree and wish further review.


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