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 1144534 [details]
foreman-debug attached

Description of problem:
Create Repo failed with : [E] RuntimeError: There was an issue with the backend service pulp: No pulp workers running.

Version-Release number of selected component (if applicable):
# rpm -qa foreman
foreman-1.11.0.9-1.el7sat.noarc

How reproducible:
everytime

Steps to Reproduce:
1.Create a product
2.Try to add repo
3.While you are adding repo, skip this and Click on the product
4.Select the product
5.Click Bulk Actions -> Remove product
6.| /opt/theforeman/tfm/root/usr/share/gems/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
2016-04-06 23:00:43 [foreman-tasks/action] [E] There was an issue with the backend service pulp: No pulp workers running. (RuntimeError)
 




Actual results:
the repo create failed

Expected results:
the repo create works

Additional info:
As, workaround I executed katello-service restart and was able to create a prod
add repo and sync it

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