Bug 1392757 - Errata skipped due to empty package list
Summary: Errata skipped due to empty package list
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 570
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 07:36 UTC by Vladimir Dulava
Modified: 2020-05-14 15:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-06 10:42:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1356241 0 unspecified CLOSED Errata skipped due to empty package list 2021-02-22 00:41:40 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.