Description of problem: After importing content from another Satellite, content views with the option "import only" are created. If one tries do sync the entire library to a capsule or promote one of those content views to a LCE that is configured to sync to a capsule, the sync will fail with 404 errors for that content view. Version-Release number of selected component (if applicable): 6.10.1 How reproducible: Steps to Reproduce: 1. Import a content view 2. Promote the content view just imported to a LCE that will sync to a capsule 3. Launch the capsule sync Actual results: Task fails with following error: Errors: 404, message='Not Found', url=URL('https://bombsat610.usersys.redhat.com/pulp/content/test_joniel/TO_SYNC/RHEL8_Kickstart/content/dist/rhel8/8.5/x86_64/baseos/kickstart')Could not lookup a publication_href for repo 188404, message='Not Found', url=URL('https://bombsat610.usersys.redhat.com/pulp/content/test_joniel/TO_SYNC/RHEL8_Kickstart/content/dist/rhel8/8.5/x86_64/appstream/kickstart')Could not lookup a publication_href for repo 189 Expected results: Sync should work. If this type of content view is not supposed to be synced, there should be something not allowing it to even try to sync (and proper documentation about it). Additional info: Creating a regular content view with the repositories provided by the imported content view and syncing works as expected.
Created redmine issue https://projects.theforeman.org/issues/34384 from this bug
Upstream bug assigned to jsherril
While the bz is being addressed upstream. You should be able to work around this issue with hammer content-view version republish-repositories --id=<version id> --force=true
*** Bug 2056568 has been marked as a duplicate of this bug. ***
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 (Moderate: Satellite 6.11 Release), 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-2022:5498