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.
DescriptionVladimír Sedmík
2021-04-06 21:04:51 UTC
Description of problem:
Orphaned content (migrated and then removed) causes failures for the final switchover to pulp3. The remediation is a cleanup prior to the switchover.
Version-Release number of selected component (if applicable):
6.9.0 snap 19.1
How reproducible:
always
Steps to Reproduce:
1. Have a SAT with yum/docker/file CVs published, run migration to pulp3.
2. Remove some of the CVs, run migration to pulp3 again.
3. Finally, run the switchover.
Actual results:
The switchover fails because of orphaned content.
Expected results:
The switchover task should handle the orphaned content.
Additional info:
The error is almost the same as BZ#1946339, however, the underlaying issue is a bit different and could be treated separately.
Comment 1Tanya Tereshchenko
2021-04-07 08:33:12 UTC
I believe pulp part is capable of handling orphaned content.
Are you talking about orphans form Katello or Pulp side?
Switchover is also a Katello operation.
The component is set to Pulp. There is nothing in this BZ, Pulp team can start working with.
Please provide logs and/or more context where the problem occurs, thanks.
Hello Tanya, I'm sorry for the confusion, I was rather talking about the Katello side and didn't distinguish it properly.
Moving to the `Content Views` component as it relates to missing CVs and adding jsherrill, who already investigated the reproducer, to the CC list.
(The fix meant for this BZ was to run foreman-rake katello:delete_orphaned_content prior to the actual switchover.)
Verified on 6.9.1 snap 2, tfm-rubygem-katello-3.18.1.27-1.el7sat.noarch
[root@satellite ~]# foreman-rake katello:pulp3_content_switchover
Checking for valid Katello configuraton.
Content Switchover completed successfully
After complete switchover all services were running, ping and health check was ok.
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 (Satellite 6.9.1 Async 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/RHBA-2021:1371