Bug 2061571
Summary: | Upgrade path 6.9 -> 6.10 -> 7.0 snap 12 broken on yum dependency on python3-pulp-2to3-migration | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> |
Component: | Documentation | Assignee: | SAT-DOCS <sat-bz-docs-list> |
Status: | CLOSED DUPLICATE | QA Contact: | SAT-DOCS <sat-bz-docs-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.11.0 | CC: | aupadhye, egolov, mdolezel |
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-09 09:48:18 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: |
Description
Pavel Moravec
2022-03-07 21:12:59 UTC
Removing the two packages (python3-pulp-2to3-migration and python2-solv) together with their dependencies (pulp-rpm-plugins and python-pulp-integrity) is a workaround. OK, the cause is I did not run foreman-maintain pulp2-remove after the upgrade to 6.10. Changing the BZ to Documentation. This step ^^ should be mentioned as a Prerequisite of Sat7.0 upgrade: "if you are upgrading Satellite that was upgraded from 6.9, run .." This is documented in the 6.9 to 6.10 upgrade docs: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite If you have migrated content from Pulp 2 to Pulp 3, remove all Pulp 2 content. # satellite-maintain content remove-pulp2 You could argue that the 6.10 to 7.0 upgrade could warn you about not having done this step (and I'd agree), but it's unrelated to 7.0 EL7toEL8 upgrades. Pavel, did you use foreman-maintain to upgrade to 7.0? Because it should have ran the pulp2 removal for you: https://github.com/theforeman/foreman_maintain/blob/master/definitions/scenarios/upgrade_to_satellite_7_0.rb#L44 (In reply to Evgeni Golov from comment #4) > Pavel, did you use foreman-maintain to upgrade to 7.0? > Yes I did: /var/log/foreman-maintain/foreman-maintain.log-20220308:I, [2022-03-07 22:21:47+0100 #23797] INFO -- : Running foreman-maintain command with arguments [["upgrade", "run", "--target-version", "7.0", "-y"]] > Because it should have ran the pulp2 removal for you: > https://github.com/theforeman/foreman_maintain/blob/master/definitions/ > scenarios/upgrade_to_satellite_7_0.rb#L44 That is not present in rubygem-foreman_maintain-1.0.3-1.el8sat.noarch : /usr/share/gems/gems/foreman_maintain-1.0.3/definitions/scenarios/upgrade_to_satellite_7_0.rb : def compose add_steps(find_procedures(:pre_migrations)) add_step(Procedures::Service::Stop.new) end end So we need to backport https://github.com/theforeman/foreman_maintain/pull/589 to Sat7.0 GA, I guess? Perfect, thanks for investigation! @aupadhye I guess we should convert this to a maintain BZ asking for the backport of https://github.com/theforeman/foreman_maintain/pull/589 to 7.0? *** This bug has been marked as a duplicate of bug 2054182 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |