Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

After registering a RHEL8 host, I tried to enable some of the available module streams. This error was displayed:

 Oops, we're sorry but something went wrong 783: unexpected token at ''

Version-Release number of selected component (if applicable):
Sat6.10 snap 10
~]# rpm -q satellite
satellite-6.10.0-0.5.beta.el7sat.noarch

How reproducible:
Happend multiple times with more than one RHEL8 host

Steps to Reproduce:
1. Create RHEL8 host
2. Register with global registration form (selecting to configure REX)
3. Navigate Hosts > Content Host, select the host
4. on the Module Stream tab attempt to enable a module stream

Actual results:

 Oops, we're sorry but something went wrong 783: unexpected token at ''

Expected results:
It works or some useful error message

Additional info:
Will attach foreman-rake errors log

I attempted to reproduce with rubygem-katello-4.1.2.1-1.el8.noarch but I didn't see the error.

Hello

looks like duplicate of
Bug 1986002 - Unable to interact with appstream actions in content host > host > appstream, leads to an oops
which was opened day before: Reported: 	2021-07-26 13:23 UTC by Jonathon Turel

Stephen, I concur. Do you want to close as a duplicate?

(In reply to James Jeffers from comment #4)
> Stephen, I concur. Do you want to close as a duplicate?

OK, will do, thank you

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