Bug 1986554

Summary: When trying to enable a module stream, 'unexpected token at "' error is displayed
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: RepositoriesAssignee: James Jeffers <jjeffers>
Status: CLOSED DUPLICATE QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: jjeffers, jsherril
Target Milestone: 6.10.0Keywords: TestBlocker, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.1.2.1-1.el8.noarch Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-10 17:16:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Wadeley 2021-07-27 18:40:28 UTC
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

Comment 2 James Jeffers 2021-08-06 15:43:49 UTC
I attempted to reproduce with rubygem-katello-4.1.2.1-1.el8.noarch but I didn't see the error.

Comment 3 Stephen Wadeley 2021-08-10 15:34:16 UTC
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

Comment 4 James Jeffers 2021-08-10 16:49:42 UTC
Stephen, I concur. Do you want to close as a duplicate?

Comment 5 Stephen Wadeley 2021-08-10 17:16:12 UTC
(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 ***