Bug 2054182
Summary: | remove pulp2 automatically on upgrade to 6.11 (If the user hasn't already done it) | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Lukas Pramuk <lpramuk> |
Component: | Satellite Maintain | Assignee: | Ian Ballou <iballou> |
Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.11.0 | CC: | apatel, aupadhye, egolov, ehelms, gtalreja, iballou, jsherril, kgaikwad, pcreech, pmoravec |
Target Milestone: | 6.11.0 | Keywords: | Regression, Triaged, UpgradeBlocker, Upgrades |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-foreman_maintain-1.0.5 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-05 14:33:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2063910 |
Description
Lukas Pramuk
2022-02-14 11:23:07 UTC
python2-solv issues is tracked by BZ #2054184 "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. *** Bug 2054184 has been marked as a duplicate of this bug. *** Created redmine issue https://projects.theforeman.org/issues/34463 from this bug Upstream bug assigned to iballou Upstream bug assigned to iballou Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34463 has been resolved. *** Bug 2061571 has been marked as a duplicate of this bug. *** @jsherril @iballou the current implementation in https://github.com/theforeman/foreman_maintain/pull/589 only runs this automatically on the Satellite, not on Capsules. The docs for the "to 6.10" upgrade document one shall run it on Capsules too: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#upgrading_capsule_server > If you have migrated content from Pulp 2 to Pulp 3, remove all Pulp 2 content. > # satellite-maintain content remove-pulp2 > This removes Pulp 2 RPMs, content in /var/lib/pulp/content/, the mongo database, and migration content in the Pulp 3 database. So I'd argue this should also automatically happen for Capsule upgrades to newer versions than 6.10? @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
Sounds good, I'll have capsules uninstall Pulp 2 as well. clearing needinfo 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 |