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:

Publishing new version of content view after Satellite upgrade from version 6.12 to 6.13 fails with below error

       Orphaned content facets for deleted hosts exist for the content view and environment. Please run rake task : katello:clean_orphaned_facets and try again!


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


Steps to Reproduce:
1. Upgrade from Satellite 6.12 to 6.13.
2. Try publishing a new version of existing content view which fails with mentioned error.


Actual results: Running "foreman-rake katello:clean_orphaned_facets" did not help and issue persist even after running the same command.


Expected results: If there are orphaned content facets in Satellite 6.12, it should get fixed or atleast detected during Satellite 6.12 to 6.13 upgrade. The issue should not be observed after successful Satellite 6.13 upgrade.

Verified on: 6.14 - Snap 5

Steps to Reproduce:
1. Create a content view and attach a RHEL 7 repo to it. Publish the CV
2. In web UI, subscribe a content host in Organization 'A' and Location 'B' to the CV.
3. In the Web UI, set your current Organization as 'A' and current Location as 'C'.
4. Publish the content view.

Actual results:
Content View is successfully published.

Expected results:
Content View is successfully published.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.14 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6818