Actions
Issue #6400
closed
relative_path for Pulp2MetadataFile is not set properly
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:
- migrate metafiles from pulp2 2, with pulp3 sync repo that contains same metafile
- 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.
Updated by ipanova@redhat.com over 4 years ago
- Status changed from NEW to POST
- Assignee set to ipanova@redhat.com
- Triaged changed from No to Yes
- Sprint set to Sprint 69
Added by ipanova@redhat.com over 4 years ago
Added by ipanova@redhat.com over 4 years ago
Revision 0ee5568b | View on GitHub
Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.
Added by ipanova@redhat.com over 4 years ago
Revision 0ee5568b | View on GitHub
Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.
Updated by ipanova@redhat.com over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|0ee5568bc023792201c4dc90b45f0a4c2c445330.
Updated by ipanova@redhat.com over 4 years ago
Applied in changeset pulp:pulp-2to3-migrate|0ee5568bc023792201c4dc90b45f0a4c2c445330.
Updated by ipanova@redhat.com over 4 years ago
Applied in changeset pulp-2to3-migration|0ee5568bc023792201c4dc90b45f0a4c2c445330.
Updated by ttereshc over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Set properly relative_path Pulp2YumRepoMetadataFile content_artifact.
closes #6400 https://pulp.plan.io/issues/6400