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.

Description of problem:
Trying to enable a rhel repo results in error 500.
(see whole traceback from production.log in attachments) 

Version-Release number of selected component (if applicable):
# rpm -qa | grep satellite
satellite-6.2.0-6.1.beta.el6sat.noarch

How reproducible:
everytime on snap 6.1

Steps to Reproduce:
1. upload a manifest
2. try to enable a rhel repo from Red Hat Repositories

Actual results:
Actions::Katello::RepositorySet::EnableRepository task results in:
500 Internal Server Error

Expected results:
repo enabled, and RH product created

Additional info:

Created attachment 1143349 [details]
/var/log/foreman/production.log

Note, this only happens on el6 version. el7 seems to be fine

This is caused by 1321644, dead pulp_workers and celery processes. Closing as a dupe

*** This bug has been marked as a duplicate of bug 1321644 ***

Updating the 'duplicate' that this bug is marked against.  The issue here appears to be related to the same as bug 1323509.

*** This bug has been marked as a duplicate of bug 1323509 ***