Bug 1392757

Summary:	Errata skipped due to empty package list
Product:	Red Hat Satellite 5	Reporter:	Vladimir Dulava <vdulava>
Component:	Satellite Synchronization	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	570	CC:	dyordano, tlestach, vdulava
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-06 10:42:58 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:

Description Vladimir Dulava 2016-11-08 07:36:42 UTC

Description of problem:
Similar to Spacewalk 2.4 bug 1356241
CU is experiencing taskomatic looping while generating repository metadata caused by "errata skipped because of empty package list."

Summary of 1356241
I'm using Pulp to download packages from Red Hat, then syncing Spacewalk with Pulp. I've found that I'm always getting an error when running spacewalk-repo-sync that erratas were skipped due to empty package list. Furthermore, when examining the Errata's that were imported, the package association is not complete. For example, RHSA-2016:1292-1 was imported, but only the RHEL7 packages were associated with the Errata, even though the associated packages were downloaded and show up in the Spacewalk channel. The only relevant error message I can seem to find is from the taskomatic log:

INFO   | jvm 1    | 2016/07/12 17:42:00 | 2016-07-12 17:42:00,121 [DefaultQuartzScheduler_Worker-4] WARN  com.redhat.rhn.taskomatic.task.ChannelRepodata - Maximum number of workers already put ... skipping. 

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomas Lestach 2016-11-08 12:21:34 UTC

The provided error message is not relevant.

I feel like 2 issues are described in this BZ. Please, report one issue/BZ.
Furthermore can you, please, provide exact reproducer steps that lead to the misbehavior?

Comment 2 Tomas Lestach 2017-03-06 10:42:58 UTC

No response for 4+ months. Closing with INSUFFICIENT_DATA.