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.
"satellite-maintain content remove-pulp2 --assumeyes" should be run by all users after upgrading to 6.10 and confirming the operation of the satellite on pulp3.
For now i would recommend you run that command after upgrading to 6.10 but before you upgrade to 7.0. That should help the upgrade go through properly, and should unblock you.
To resolve this, we will add a step to the upgrade to 7.0 to automatically run this command for the user.
@egolov Thanks. Lets speed it up. No needinfos needed as I'm failing QA for this BZ.
FailedQA.
@Satellite 7.0.0 Snap13
by just sanity checking the foreman-maintain source:
>>> the same changes in definitions/scenarios/upgrade_to_satellite_7_0.rb should've gone also to definitions/scenarios/upgrade_to_capsule_7_0.rb
VERIFIED.
@Satellite 6.11.0 Snap16
rubygem-foreman_maintain-1.0.7-1.el7sat.noarch
by the manual reproducer described in comment#0:
1) Have a Sat 6.9.9 and Capsule 6.9.9 associated
2) Upgrade both Satellite and Capsule to 6.10.4 (upgraded from 6.9 => python3-pulp-2to3-migration is present)
3) Upgrade both Satellite and Capsule to 6.11.0
# satellite-maintain upgrade run --target-version 6.11 -w repositories-validate,repositories-setup -y
...
--------------------------------------------------------------------------------
Upgrade finished.
>>> upgrade is now successful as there are no failed rpm dependencies
# rpm -q python3-pulp-2to3-migration
package python3-pulp-2to3-migration is not installed
>>> pulp2 removal is now performed automatically upon 6.11 upgrade (on both Satellite and Capsule)
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
Description of problem: python3-pulp-2to3-migration rpm prevents upgrades to solve dependencies as python3-pulp-2to3-migration requirement for "python3-pulpcore < 3.15" conflicts with tfm-pulpcore-python3-pulpcore-3.16 rpm Version-Release number of selected component (if applicable): 7.0.0 How reproducible: deterministic Steps to Reproduce: 1. Have a Sat 6.10.2 (upgraded from 6.9 so it content migration was performed = python3-pulp-2to3-migration is present) # rpm -q python3-pulp-2to3-migration python3-pulp-2to3-migration-0.12.0-1.el7pc.noarch 2. Upgrade to 7.0.0 # satellite-maintain upgrade run --target-version 7.0 -w repositories-validate,repositories-setup -y ... Running Migration scripts to Satellite 7.0 ================================================================================ Setup repositories: [SKIPPED] -------------------------------------------------------------------------------- Unlock packages: [OK] -------------------------------------------------------------------------------- Update package(s) : [FAIL] Failed executing yum -y --disableplugin=foreman-protector update, exit status 1: Loaded plugins: product-id, search-disabled-repos, subscription-manager Resolving Dependencies --> Running transaction check ... Error: Package: python2-solv-0.7.20-1.el7pc.x86_64 (@rhel-7-server-satellite-6.10-rpms) Requires: libsolv(x86-64) = 0.7.20-1.el7pc Removing: libsolv-0.7.20-1.el7pc.x86_64 (@rhel-7-server-satellite-6.10-rpms) libsolv(x86-64) = 0.7.20-1.el7pc Updated By: libsolv-0.7.20-4.el7pc.x86_64 (rhel-7-server-satellite-7.0-rpms) libsolv(x86-64) = 0.7.20-4.el7pc Available: libsolv-0.6.11-1.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.11-1.el7 Available: libsolv-0.6.20-5.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.20-5.el7 Available: libsolv-0.6.26-1.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.26-1.el7 Available: libsolv-0.6.26-2.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.26-2.el7 Available: libsolv-0.6.34-2.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.34-2.el7 Available: libsolv-0.6.34-4.el7.x86_64 (rhel-7-server-rpms) libsolv(x86-64) = 0.6.34-4.el7 Error: Package: python3-pulp-2to3-migration-0.12.0-1.el7pc.noarch (@rhel-7-server-satellite-6.10-rpms) Requires: python3-pulpcore >= 3.13 Removing: python3-pulpcore-3.14.9-1.el7pc.noarch (@rhel-7-server-satellite-6.10-rpms) python3-pulpcore = 3.14.9-1.el7pc Obsoleted By: tfm-pulpcore-python3-pulpcore-3.16.1-1.el7pc.noarch (rhel-7-server-satellite-7.0-rpms) Not found Error: Package: python3-pulp-2to3-migration-0.12.0-1.el7pc.noarch (@rhel-7-server-satellite-6.10-rpms) Requires: python3-pulpcore < 3.15 Removing: python3-pulpcore-3.14.9-1.el7pc.noarch (@rhel-7-server-satellite-6.10-rpms) python3-pulpcore = 3.14.9-1.el7pc Obsoleted By: tfm-pulpcore-python3-pulpcore-3.16.1-1.el7pc.noarch (rhel-7-server-satellite-7.0-rpms) Not found Actual results: upgrade failed to solve dependencies Expected results: upgrade is successful Additional info: the output shows there is yet another issue: python2-solv => yet another BZ