Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1282855

Summary:	spacewalk-clone-by-date is slow (5 hrs) for some cloned channels
Product:	[Community] Spacewalk	Reporter:	Grant Gainey <ggainey>
Component:	Server	Assignee:	Grant Gainey <ggainey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.4	CC:	dyordano, ggainey, mmello, nkim, pgervase, satqe-list, tkasparek, tlestach, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	spacewalk-java-2.5.12-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1277251	Environment:
Last Closed:	2016-06-16 07:54:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1484117

Comment 1 Grant Gainey 2015-11-17 16:27:47 UTC

The "some channels" slowness was to a large degree due to suboptimal code in Erratafactory.publishToChannel(), when dealing with cloning of cloned-channels.


spacewalk.github: 7da7fd59d23e1f1d45a996d6b0f18bd04a8deeae

Comment 4 Tomáš Kašpárek 2016-06-16 07:54:28 UTC

Spacewalk 2.5 was released.

Comment 5 Eric Herget 2017-09-28 18:07:02 UTC

This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.