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.
DescriptionJustin Sherrill
2021-05-27 18:48:21 UTC
Description of problem:
If on a satellite you have two different products with a repository with the same label, for example:
Product A
Repo w/ label: foo
Product B
Repo w/ label: foo
and you publish both of these in the same Content view with label 'bar'. OR
You have such things in two different orgs, and you publish them in two different content views with the same label. Migration will succeed, but content-stats will show:
============Migration Summary================
Migrated/Total RPMs: 32/32
Migrated/Total errata: 3/3
Migrated/Total repositories: 4/6
Notice that only 2 out of 4 repos are migrated! If you try to do a switchover, it will fail with:
Failed executing foreman-rake katello:pulp3_post_migration_check, exit status 1:
ERROR: yum repositories with ID [42880,42948,42418,42600,42238,30634,28592] have a NULL value for version_href
How reproducible:
always
Steps to Reproduce:
1. Create ProductA
2. Create a repo in ProductA with label 'foo' pointed to some repo, sync it
3. Create Product B
4. Create a repo in ProductB with label 'foo' pointed to some repo, sync it
5. Add both 'foo' repos to a content view and publish it
6. run foreman-rake content prepare
7. run foreman-rake content migration-stats
notice that not all repos are migrated
Steps to test:
1. Create ProductA
2. Create a repo in ProductA with label 'foo' pointed to some repo, sync it
3. Create Product B
4. Create a repo in ProductB with label 'foo' pointed to same repo as 2, sync it
5. Create Product C
6. Create a repo in ProductC with label 'foo' pointed to some repo, sync it
7. Add both 'foo' repos to a content view and publish it
8. run satellite-maintain prep-6.10-upgrade
9. run satellite-maintain content prepare
10. run satellite-maintain content migration-stats
Expected result:
Migrated/Total RPMs: 64/64
Migrated/Total errata: 36/36
Migrated/Total repositories: 9/9
Actual result:
Migrated/Total RPMs: 64/64
Migrated/Total errata: 36/36
Migrated/Total repositories: 9/9
Verified on 6.9.5 snap 1 with tfm-rubygem-katello-3.18.1.36-1.el7sat.noarch
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.5 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:3387