Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Import fails to connect collection version and metadata content #1836

Closed
mdellweg opened this issue May 7, 2024 · 1 comment · Fixed by #1837
Closed

Import fails to connect collection version and metadata content #1836

mdellweg opened this issue May 7, 2024 · 1 comment · Fixed by #1837
Labels
Issue Triage-Needed

Comments

@mdellweg
Copy link
Member

mdellweg commented May 7, 2024

Version

Describe the bug
Import fails to associate signatures (and probably other content) to collection versions.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.
mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue May 7, 2024
@mdellweg
Fix import collection marks and signatures
34ff5a2 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes pulp#1836
@mdellweg mdellweg mentioned this issue May 7, 2024
Merged
@pulpbot pulpbot moved this to Needs review in RH Pulp Kanban board May 7, 2024
mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
5fb630b 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

This accidentally also fixes the deprecation content api, since it was
needed in the tests.

fixes pulp#1836
mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
723497b 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

This accidentally also fixes the deprecation content api, since it was
needed in the tests.

fixes pulp#1836
mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
d9cd22f 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes pulp#1836
mdellweg added a commit that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
4cf073b 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836
patchback bot pushed a commit that referenced this issue May 8, 2024
@mdellweg @patchback
Fix import collection marks and signatures
4775b07 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
@pulpbot pulpbot moved this from Needs review to Done in RH Pulp Kanban board May 8, 2024
@patchback patchback bot mentioned this issue May 8, 2024
Merged
mdellweg added a commit to mdellweg/pulp_ansible that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
8fff73f 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes pulp#1836

(cherry picked from commit 4cf073b)
@mdellweg mdellweg mentioned this issue May 8, 2024
Merged
mdellweg added a commit that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
390b92d 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
patchback bot pushed a commit that referenced this issue May 8, 2024
@mdellweg @patchback
Fix import collection marks and signatures
f208927 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
(cherry picked from commit 390b92d)
@patchback patchback bot mentioned this issue May 8, 2024
Merged
mdellweg added a commit that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
51a436d 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
(cherry picked from commit 390b92d)
mdellweg added a commit that referenced this issue May 8, 2024
@mdellweg
Fix import collection marks and signatures
70e7be5 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
@pulpbot
Copy link
Member

pulpbot commented May 15, 2024

https://bugzilla.redhat.com/show_bug.cgi?id=2279069

patchback bot pushed a commit that referenced this issue Aug 14, 2024
@mdellweg @patchback
Fix import collection marks and signatures
d573d6a 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
@patchback patchback bot mentioned this issue Aug 14, 2024
Merged
mdellweg added a commit that referenced this issue Aug 14, 2024
@mdellweg
Fix import collection marks and signatures
9b6bd01 
The import code was unable to link up a collection version with its
metadata because using multiple fields as a foreign key is not supported
by django-import-export. The only viable fallback given existing export
files is to use the upstream_id.

fixes #1836

(cherry picked from commit 4cf073b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue Triage-Needed
Projects
No open projects
RH Pulp Kanban board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix import collection marks and signatures mdellweg/pulp_ansible
2 participants
@pulpbot @mdellweg