Project

Profile

Help

Issue #6400

relative_path for Pulp2MetadataFile is not set properly

Added by ipanova@redhat.com 9 days ago. Updated 8 days ago.

Status:
MODIFIED
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
Severity:
2. Medium
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 69

Description

As a result content artifact contains incorrect relative_path, which leads to an error when these steps are performed:

  1. migrate metafiles from pulp2 2, with pulp3 sync repo that contains same metafile
  2. observe error: "No declared artifact with relative path \"productid\" for content \"<RepoMetadataFile: pk=b21ceccf-f6e6-44dd-8f93-6677954c4456>\"",

Also because of this incorectness publish would produce wrong repo metadata.

Associated revisions

Revision 0ee5568b View on GitHub
Added by ipanova@redhat.com 9 days ago

Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.

closes #6400 https://pulp.plan.io/issues/6400

Revision 0ee5568b View on GitHub
Added by ipanova@redhat.com 9 days ago

Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.

closes #6400 https://pulp.plan.io/issues/6400

History

#1 Updated by ipanova@redhat.com 9 days ago

  • Status changed from NEW to POST
  • Assignee set to ipanova@redhat.com
  • Triaged changed from No to Yes
  • Sprint set to Sprint 69

#2 Updated by ipanova@redhat.com 9 days ago

  • Status changed from POST to MODIFIED

Please register to edit this issue

Also available in: Atom PDF