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.
hammer content-import fails with error Export version 3.14.9 of pulpcore does not match installed version 3.14.12 if the z-stream versions are different for the connected and disconnected satellite 6.10
Verified.
Tested Satellite 6.10.7.2 Snap 1.0
Version: python3-pulpcore-3.14.19-2.el7pc.noarch
Steps:
1. Spin up a satellite to export that has a Pulp version less than python3-pulpcore-3.14.19-2, mine was python3-pulpcore-3.14.9-1 (Satellite 6.10.2)
2. Import a manifest
3. Set download policy to "immediate"
4. Sync an RHEL7 server repo
5. Create a cv, add the repo from step 4, and publish the cv
6. Run content-export
7. Spin up a satellite for a disconnected mode that has python3-pulpcore-3.14.19-2 or greater
8. Import manifest
9. Go to Settings -> Content -> Disconnected Mode -> Set False
10. Go to Settings -> Content -> Default Red Hat Repository download policy -> Set "Immediate"
11. SCP exported to disconnected satellite
12. Run content-import on disconnected satellite
Observation:
Content import on disconnected Satellite was completed successfully, without any errors.
And, tried to import the same content on older 6.10.4, and was able to reproduce the issue.
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.10.7.2 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-2023:1041