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 1043534 [details]
production.log

Description of problem:
Repository creation failed with pulp connection issue

Version-Release number of selected component (if applicable):
Sat 6.1.1 GA Snap 2

How reproducible:
Always

Steps to Reproduce:
1. Create a repository in UI

Actual results:
Errored (screenshot attached)

Expected results:
No error

Additional info:
This is found in automation box. I am not attaching a foreman-debug as that may contain a lot of irrelevant data. Instead I am attaching the production.log

Created attachment 1043535 [details]
UI error on repo creation

Also content publishing fails

A foreman-debug for this would be more helpful as it will include Pulp logs among other things.

wasn't able to see much in the logs, but restarting all the pulp services seemed to resolve this.

As per Comment 5 - restarting pulp resolved this issue - but I reinstalled this machine twice and got this same error.  So something is going wrong - probably with either
1. the new code which checks the backend services before triggering actions (or)
2. perhaps a required service wasn't started properly

I have attached foreman-debug (collected after jsherrill's restart of pulp services) here.  Please let me know what is going wrong here.

This

Verified.  Automation did not throw this error in Sat 6.1 GA Snap 11.

*** Bug 1236708 has been marked as a duplicate of this bug. ***

This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.