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:
When try to create new Docker repository, getting:
"There was an issue with the backend service pulp: No pulp workers running."

Issue is not specific to UI, API or CLI as can be reproduced through all of them

Issue is also not specific to RHEL6 or RHEL7 as can be reproduced on both

Version-Release number of selected component (if applicable):
Sat6.2 SNAP 6.1

How reproducible:
Always

Steps to Reproduce:
1. Try to create new docker repository using https://registry-1.docker.io and 'busybox' repository

Actual results:
Error is raised

Expected results:
Repository is created

Additional info:

Created attachment 1143856 [details]
Screenshot with issue for UI

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

The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

The Pulp upstream bug priority is at High. Updating the external tracker on this bug.