Actions
Issue #4268
closed
Publishing a repo in-place multiple times creates multiple modules.yaml archives
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 47
Quarter:
Description
Even if nothing has changed in the repository, publishing an RPM repository several times will result in multiple modules.yaml.gz archives, even if the repository has no modules data (the modules.tar.gz archives are all empty), and each has different hashes.
Files
Related issues
Updated by CodeHeeler about 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 46
Updated by dalley about 6 years ago
- Subject changed from Publishing a repo in-place creates multiple modules.yaml archives to Publishing a repo in-place multiple times creates multiple modules.yaml archives
Updated by CodeHeeler almost 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to CodeHeeler
Updated by dalley almost 6 years ago
- Related to Issue #4252: modules.yaml file is generated on repository with no modularity information added
Updated by CodeHeeler almost 6 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
CodeHeeler)
Updated by dalley almost 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by dalley almost 6 years ago
- Status changed from ASSIGNED to POST
Updated by dalley almost 6 years ago
- Status changed from POST to CLOSED - NOTABUG
I believe this is actually not an issue. Only one file is listed in repomd.xml. The OldRepoData cleanup step should take care of this just like everything else.
Actions
.