Bug 1996476
| Summary: | Failed executing foreman-rake katello:pulp3_migration, exit status 1: rake aborted! | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Taft Sanders <tasander> |
| Component: | Satellite Maintain | Assignee: | Amit Upadhye <aupadhye> |
| Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | apatel, aupadhye, ehelms, jsherril, kgaikwad, osousa, pcreech |
| Target Milestone: | 6.10.0 | Keywords: | Triaged, Upgrades |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-foreman_maintain-0.8.14 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 13:48:21 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: | |||
Verified. Tested on Satellite 6.10.0 Snap 17.0 Version: rubygem-foreman_maintain-0.8.14-1.el7sat.noarch Steps: 1. Perform pulp2to3 migration 2. Run twice # foreman-maintain upgrade run --target-version 6.10 --whitelist="repositories-validate" (Fails post-switchover for repositories-setup) Observation: For the first time, the switchover completes, the second time switchover gets skipped. If the upgrade fails post-switchover/post-package upgrade, suppose in installer like BZ[1] with packages updated including satellite and katello, so content-switchover step will be skipped from that scenario if a version of katello > 4.0 [1] https://bugzilla.redhat.com/show_bug.cgi?id=2001229 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 |
Description of problem: During the upgrade the beta repos were set and the environment variable "FOREMAN_MAINTAIN_USE_BETA='1'" was not used. To work around this the whitelist option of 'repositories-validate' was used. After the pulp3 migration completed the installer runs again to upgrade with pulp3 settings. Once the installer reaches the point of: Re-running the installer to switch specified content over to pulp3 [OK] -------------------------------------------------------------------------------- Setup repositories: the installer fails because the name of this whitelist step is 'repositories-setup'. After adding this step to the whitelist options and running again, the installer fails to run continuously because the content is already migrated but the migration steps from the installer are still being called every time. Version-Release number of selected component (if applicable): 6.10.0 Snap14 How reproducible: Every time Steps to Reproduce: 1. Do not use standard repositories or environment variable "FOREMAN_MAINTAIN_USE_BETA='1'" or figure out another way to cause the installer to fail AFTER the pulp migration 2. Upgrade using installer option '--whitelist="repositories-validate"' 3. Actual results: Installer fails continuously because pulp content is already migrated Expected results: After the pulp content is upgraded and the installer re-runs to upgrade the Satellite with pulp3 as seen here in this step: =============================== Starting the following service(s): pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4 / All services started [OK] -------------------------------------------------------------------------------- Switch support for certain content from Pulp 2 to Pulp 3: Performing final content migration before switching content Checking for valid Katello configuraton. Starting task. 2021-08-22 14:27:36 -0400: Importing migrated content type erratum: 14000/12657 Content Migration completed successfully Performing a check to verify everything that is needed has been migrated Switching specified content over to pulp 3 Checking for valid Katello configuraton. Content Switchover completed successfully Re-running the installer to switch specified content over to pulp3 [OK] =============================== The installer should be able to detect that the pulp migration has completed and is not needed again. Additional info: After hitting this, setting the environment variable "FOREMAN_MAINTAIN_USE_BETA='1'" and/or including the whitelist value 'repositories-setup' has no effect on the failing outcome of the upgrade. This suggests that currently, at this point or any other point in the re-run of the upgrade after the migration will indefinitely fail the upgrade. Whitelisting this step appears to be the only way to continue forward with the upgrade which results in the failure of the pulp3 migration and hammer ping being the next failure step in the upgrade: # hammer ping database: Status: ok Server Response: Duration: 0ms candlepin: Status: ok Server Response: Duration: 38ms candlepin_events: Status: ok message: 0 Processed, 0 Failed Server Response: Duration: 0ms candlepin_auth: Status: ok Server Response: Duration: 35ms katello_events: Status: ok message: 0 Processed, 0 Failed Server Response: Duration: 0ms pulp: Status: ok Server Response: Duration: 100ms pulp_auth: Status: ok Server Response: Duration: 43ms pulp3: Status: FAIL Server Response: Message: 503 Service Unavailable foreman_tasks: Status: ok Server Response: Duration: 3ms