Story #6558
Story #6134: [EPIC] Pulp import/export
As a user, I receive an error message if I try to import an export from a Pulp instance with a different version
100%
Description
We need to store the version information of the exporting Pulp instance in the export archive. Then compare it to the importing Pulp instance when importing.
This probably should also extend to any plugin whose data is included in the export.
Associated revisions
History
#2
Updated by daviddavis about 2 months ago
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
#3
Updated by daviddavis about 2 months ago
- File deleted (
clipboard-202004301711-yqmyw.png)
#4
Updated by daviddavis about 2 months ago
- File deleted (
clipboard-202004301712-rps6t.png)
#5
Updated by daviddavis about 2 months ago
I'm not sure how restrictive to make this check (ie should I match the version exactly or perhaps to something like the y-stream)?
#6
Updated by daviddavis about 1 month ago
- Status changed from ASSIGNED to POST
#7
Updated by ggainey about 1 month ago
- Sprint set to Sprint 73
#8
Updated by pulpbot about 1 month ago
#9
Updated by daviddavis about 1 month ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|2846c77f7fbfdb288ef8efd9d2aa1683618107d7.
#10
Updated by BarbaraPerry about 1 month ago
This kind of error can be occurred due to using of wrong command while importing or exporting of data. If you can go through the material present https://www.assignmentgeek.com.au/ writing service blog that helps you in using right command and solve your error problem also. There two different commands should be used for import and export.
#11
Updated by dkliban@redhat.com about 1 month ago
- Sprint/Milestone set to 3.4.0
#12
Updated by dkliban@redhat.com about 1 month ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
.
Add version checking to import
fixes #6558