Bug 1929380
| Summary: | pulp3: Handle migration when same distributor is being re-used for different repositories in between the plans | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Tanya Tereshchenko <ttereshc> |
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9.0 | CC: | bmbouter, ggainey, ipanova, pcreech, rchan, ttereshc |
| Target Milestone: | 6.9.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-pulp_2to3_migration-0.9.0-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-04-21 13:10:34 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: | |||
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. I have checked that the code is in the build and none of it is missing. Verified on 6.9.0_017 with python3-pulp-2to3-migration-0.9.1-1.el7pc.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 (Moderate: Satellite 6.9 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-2021:1313 |
Description of problem: There is a correctness problem when distributors are reused between two different migration plans. Create plan and run: { "plan": { "plugins": [ { "repositories": [ { "name": "file", "pulp2_importer_repository_id": "file", "repository_versions": [ { "pulp2_distributor_repository_ids": [ "file2" ], "pulp2_repository_id": "file" } ] }, { "name": "file2", "pulp2_importer_repository_id": "file2", "repository_versions": [ { "pulp2_distributor_repository_ids": [ "file-many" ], "pulp2_repository_id": "file2" } ] } ], "type": "iso" } ] }, Create another plan and run: { "plan": { "plugins": [ { "repositories": [ { "name": "file", "pulp2_importer_repository_id": "file", "repository_versions": [ { "pulp2_distributor_repository_ids": [ "file-many" ], "pulp2_repository_id": "file" } ] }, { "name": "file2", "pulp2_importer_repository_id": "file2", "repository_versions": [ { "pulp2_distributor_repository_ids": [ "file-large" ], "pulp2_repository_id": "file2" } ] } ], "type": "iso" } ] }, File2 repo will have 2 distributions displayed file-large and file-many. In addition there is a concern of hitting base_path collision because same distributor file-many has been used to distribute 2 different repos. NOTE: Importers will suffer as well from correctness problem in case same importer will be used for 2 different repos in between the migration plans ### Another way to grasp the problem Imagine when two distributors are being swapped. First migration plan/run: repo A with dist A repo B with dist B Second migration plan/run: repo A with dist B repo B with dist A