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 1021900 [details]
Traceback

Description of problem:

While enabling repositories, it was failing with a "500: Internal Server Error".

Version-Release number of selected component (if applicable):
Satellite 6.1 beta

How reproducible:
Not sure.

Steps to Reproduce:
1. Import a manifest (Content -> Red Hat Subscriptions)
2. Attempt to enable a repository (Content -> Red Hat Repositories)

Actual results:
500 ISE

Expected results:
No error

Additional info:

Note: it was observed that refreshing the manifest resolved the issue.

This issue was raised by AshishH during a Sat 6.1 Beta test day.

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.

tested on 6.1 Snap 8 Compose 3 and could not reproduce this issue.

Verified. This works fine for me.

I saw a similar error when trying to upload an old manifest, but I figured that the manifest's corresponding satellite entry had been removed from portal.

I will reopen this issue if I see it happening again.

Does this require a rel note something like "if you run into this issue try refreshing (recreating?) your manifest"?

Otherwise, is a rel note required at all?

thanks

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