Issue #2379
closed
repomd.xml points to wrong updateinfo.xml.gz file
Status:
CLOSED - WORKSFORME
Description
As Issue #2096 identifies, each incremental publish leaves a copy of updateinfo.xml.gz in the repodata folder. The repomd.xml file sometimes links to the wrong updateinof.xml.gz file. If that incremental publish brings in additional errata then those errata will not be published.
- Subject changed from repo.md uses wrong updateinfo.xml.gz file to repomd.xml points to wrong updateinfo.xml.gz file
- Description updated (diff)
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Priority changed from High to Urgent
- Sprint/Milestone set to 28
- Platform Release set to 2.10.2
- Triaged changed from No to Yes
This is listed as a release blocker against 2.10.2, but as far as I can tell we've been doing this wrong for a while. I'd like to reconsider blocking 2.10.2 on this issue and instead plan to include this in 2.10.3, unless this is specifically introduces a regression between 2.10.0 and 2.10.1.
tl;dr This issue should not block 2.10.2
Two updates on this issue.
1. the reproducer I was using did not make the correct assertion at the end, and when I fixed that I could not reproduce the issue on upstream Pulp as I thought I could.
2. The updated reproducer did reproduce an issue on a downstream install. I believe this issue is only affecting downstream. I should have a better understanding of why soon. I'm debugging the reproducer box now.
- File deleted (
1088_reproducer.py)
- Status changed from ASSIGNED to CLOSED - WORKSFORME
After a lot of testing I cannot reproduce this issue on upstream Pulp
- Platform Release deleted (
2.10.2)
- Sprint/Milestone deleted (
28)
Also available in: Atom
PDF
.