Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 945306[details]
Forman Debug info
Description of problem:
When publishing a new version of a Content View while multiple large sync jobs are running simultanously the Content View Publish job get "stuck" most likely it is on the queue waiting for someone to pick the task and complete it. Seems like all the workers are busy doing sync, and the Content View publish task is left in the queue until there are available workers.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Start syncronization of some large repos. Examples:
Red Hat Enterprise Linux 6 Server - Optional RPMs x86_64 6Server
Red Hat Enterprise Linux 6 Server - Supplementary RPMs x86_64 6Server
etc.
2. Make change to a Content View.
3. Publish new version of Content View.
Actual results:
Content View Publish task starts, but is stuck on copy rpms step.
If Sync jobs are cancelled, Content View Publish Task continues.
Expected results:
Content View Publish Task completes in a few minutes, as it does when no sync is on-going.
Additional info:
Comment 1RHEL Program Management
2014-10-09 13:13:15 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I have tested this on Satellite 6.2 GA and am unable to reproduce the behavior described. There have been numerous improvements in this area, since the bug was initially created; therefore, I am going to close it out. If you re-encounter this issue on Satellite 6.2, please open a new bugzilla and attach updated foreman-debug with full details. Thanks!
Created attachment 945306 [details] Forman Debug info Description of problem: When publishing a new version of a Content View while multiple large sync jobs are running simultanously the Content View Publish job get "stuck" most likely it is on the queue waiting for someone to pick the task and complete it. Seems like all the workers are busy doing sync, and the Content View publish task is left in the queue until there are available workers. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start syncronization of some large repos. Examples: Red Hat Enterprise Linux 6 Server - Optional RPMs x86_64 6Server Red Hat Enterprise Linux 6 Server - Supplementary RPMs x86_64 6Server etc. 2. Make change to a Content View. 3. Publish new version of Content View. Actual results: Content View Publish task starts, but is stuck on copy rpms step. If Sync jobs are cancelled, Content View Publish Task continues. Expected results: Content View Publish Task completes in a few minutes, as it does when no sync is on-going. Additional info: