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.

Created attachment 1196890 [details]
console error

Description of problem:
When trying to view/edit a content view in the UI, the content view doesn't load. When opening a web console, the following error is seen "bastion-c18774b….js:2 ReferenceError: contentViewId is not defined". See attached for screenshot of detailed error.

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

How reproducible:
Always

Steps to Reproduce:
Create a content view.
or
Click an existing content view from the list.

Actual results:
Content view details do not show. Error is seen in console.

Expected results:
No errors seen and content view page works correctly.

Additional info:
bastion-c18774b….js:2 ReferenceError: contentViewId is not defined
    at new <anonymous> (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion_katello/bastion…5b8d81ee6eb413e8321a6a921b09efd0b1040ae727255959f8c3502469c5ea7.js:3:14602)
    at r (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:1:29893)
    at Object.a [as instantiate] (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:1:30005)
    at https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:2:13370
    at https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:5:10838
    at g (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:2:6682)
    at l (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:2:2907)
    at https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:2:2576
    at u (https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:5:10081)
    at https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/assets/bastion/bastion-c18774b2f4243bbfc3b1179d9ebfa1ee18218f69ba2ce552f356ed276a1735f4.js:5:10350 <span class="action-panel ng-scope" ui-view="action-panel">

This is a "duplicate" of bug #1117753.  This problem was caused by not including the fix for bug #1117753 while including the fix for bug #1257586 which was based off of code in the former bug.  

This will be implicitly verified when verifying bug #1117753 and bug #1257586.

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