Bug 2025804
| Summary: | Option "Verify Checksum" not listed under Advanced Sync Options | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Taft Sanders <tasander> | ||||||
| Component: | Repositories | Assignee: | Ian Ballou <iballou> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.9.6 | CC: | ahumbe, iballou, jsherril, osousa, vijsingh | ||||||
| Target Milestone: | 6.9.9 | Keywords: | EasyFix, Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | tfm-rubygem-katello-3.18.1.51-1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 2027816 (view as bug list) | Environment: | |||||||
| Last Closed: | 2022-04-20 20:34:52 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1843098 [details]
repository select action menu
Created attachment 1843099 [details]
Advanced Sync Options
The option is now available in 2 places, under advanced content sync its called 'validate content sync', under the actions drop down its called 'verify content checksum'. In 6.10 the first place has been removed since it is no longer a 'sync' with pulp3. We'll adjust the verbage in satellite-maintain output *** Bug 2027816 has been marked as a duplicate of this bug. *** Applicable only to 6.9.z. 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/34112 has been resolved. Verified. Tested on Satellite 6.9.9 Snap 1.0 Version: tfm-rubygem-katello-3.18.1.53-1.el7sat.noarch Steps: 1. Sync some repositories with an immediate download policy, and publish them in CV. 2. 'corrupt' some files in /var/lib/pulp/content/ by either deleting them or echo'ing extra data to them like "echo foobar >> /var/lib/pulp/content/path/to/file.rpm" 3. # foreman-maintain content prepare 4. # foreman-maintain content migration-stats Observation: Content prepare fails when finds corrupt content and migration-stats shows the steps to resolve where earlier Option "Verify Checksum" was listed which isn't available under Advanced Sync Options In the migration-stats resolution steps, the option "Verify Checksum" is renamed to "Validate Content Sync", which can be found under Advanced Sync Options. Also tested "Validate Content Sync" for resolving corrupted content, and it works. 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 (Important: Satellite 6.9.9 Async Bug Fix Update), 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:1478 |
Description of problem: During the Pulp2to3 migration, if the content is found to be corrupted or missing the error message below is seen. Option 1 suggests an option that is not an option under the Advance Sync Options as seen in the attached screenshots. Version-Release number of selected component (if applicable): 6.9.6 How reproducible: Every time Steps to Reproduce: 1. Break an RPM on your Satellite 2. Migrate Content 3. See options to fix them Actual results: ============Missing/Corrupted Content Summary================ WARNING: MISSING OR CORRUPTED CONTENT DETECTED Corrupted or Missing Rpm: 2123/130887 Corrupted or missing content has been detected, you can examine the list of content in /tmp/unmigratable_content-20211116-130423-1879gdc and take action by either: 1. Performing a 'Verify Checksum' sync under Advanced Sync Options, let it complete, and re-running the migration 2. Deleting/disabling the affected repositories and running orphan cleanup (foreman-rake katello:delete_orphaned_content) and re-running the migration 3. Manually correcting files on the filesystem in /var/lib/pulp/content/ and re-running the migration 4. Mark currently corrupted or missing content as skipped (foreman-rake katello:approve_corrupted_migration_content). This will skip migration of missing or corrupted content. [OK] -------------------------------------------------------------------------------- Expected results: The option should be Satellite WebUI > Product > Repository > Select Action > Advanced Sync > Validate Content Sync or Satellite WebUI > Product > Repository > Verify Content Checksum Additional info: