Project

Profile

Help

Issue #6400

relative_path for Pulp2MetadataFile is not set properly

Added by ipanova@redhat.com over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 69
Quarter:

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 over 1 year 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 over 1 year 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 over 1 year ago

Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.

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

History

#1 Updated by ipanova@redhat.com over 1 year 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 over 1 year ago

  • Status changed from POST to MODIFIED

#5 Updated by ttereshc over 1 year ago

  • Sprint/Milestone set to 0.2.0

#6 Updated by ttereshc over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF