Bug 1985165
| Summary: | Pulp2 to Pulp3 Content switchover failed in the satellite upgrade | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> | |
| Component: | Satellite Maintain | Assignee: | Justin Sherrill <jsherril> | |
| Status: | CLOSED ERRATA | QA Contact: | Devendra Singh <desingh> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.10.0 | CC: | apatel, aupadhye, gtalreja, jsherril, kgaikwad, osousa | |
| Target Milestone: | 6.10.0 | Keywords: | AutomationBlocker, Regression, Triaged, UpgradeBlocker | |
| Target Release: | Unused | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | rubygem-foreman_maintain-0.8.9 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1998223 (view as bug list) | Environment: | ||
| Last Closed: | 2021-11-16 13:48:19 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
Devendra Singh
2021-07-23 03:46:23 UTC
I'm noticing a couple things going on: 1. the initial migration is failing with: Some corrupted or missing content found, run 'foreman-maintain content migration-stats' for more information. I dont' see any call to 'foreman-rake katello:approve_corrupted_migration_content' to approve the corrupted or missing content. 2. This is causing the 'content prepare' command to leave the worker services running (approve_corrupted_migration_content won't actually fix that, unsure if this really needs fixing) 3. When the upgrade shuts down all its services, it properly detects that pulpcore-api needs shutting down, but not the pulpcore-workers so they are left running. At the end however, redis is shut down which causes the workers to die 4. Eventually redis is started, but the workers are already dead and work is assigned to it (https://pulp.plan.io/issues/5906 may help with this, unsure since pulp hasn't realized the workers are dead). let me dig into 3) as i think that will help quite a bit one thing to be clear though, you will need to update automation to run 'foreman-rake katello:approve_corrupted_migration_content' if there is missing or corrupt content on the filesystem. The upgrade will not proceed if you have missing/corrupt content and have not explicitly approved it. Connecting redmine issue https://projects.theforeman.org/issues/33149 from this bug A simple workaround should be to run this prior to running the upgrade: systemctl stop pulpcore-worker@1 pulpcore-worker@2 pulpcore-worker@3 pulpcore-worker@4 I'm in the middle of testing the fix to 100% confirm this. Verified on 6.10 Snap12. Verification points: 1. Prepared the 6.9.z setup using the upgrade template. 2. Ran the pulp migration. 3. Pulp migration and it completes successfully. 4. Ran the upgrade from 6.9.z to 6.10 Snap12 and it has been completed successfully. foreman-maintain upgrade run --whitelist="disk-performance" --target-version 6.10 -y ........... ........... Running Checks before upgrading to Satellite 6.10 ....... Unlock packages: [32m[1m[OK][0m -------------------------------------------------------------------------------- Update package(s) : [32m[1m[OK][0m -------------------------------------------------------------------------------- Procedures::Installer::Upgrade: [32m[1m[OK][0m -------------------------------------------------------------------------------- Execute upgrade:run rake task: [32m[1m[OK][0m -------------------------------------------------------------------------------- Running Procedures after migrating to Satellite 6.10 ================================================================================ Refresh detected features: [32m[1m[OK][0m -------------------------------------------------------------------------------- Start applicable services: ............. ............. Upgrade finished. 5. Verified the fixed in version. # rpm -qa|grep rubygem-foreman_maintain rubygem-foreman_maintain-0.8.10-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.10 Satellite Maintenance 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/RHBA-2021:4697 |