Issue #1926
closed
package without epoch in the erratum pkglist is not handled correctly during publish
Status:
CLOSED - CURRENTRELEASE
Description
Create repo with feed https://repos.fedorapeople.org/pulp/pulp/fixtures/rpm/ and sync/publish it.
Since our demo repo does not contain `epoch` for packages in updateinfo.xml, there will be a `null` value for epoch in the erratum pkglist in the database.
This will cause a DB query which checks the presence of the particular rpm in the repo to be wrong and thus you will observe no packages in the updateinfo.xml after publish.
Should the epoch attribute be always present in the erratum pkglist for each package? If so, it is a problem of demo repo and not a bug in Pulp.
Or should we handle this case during sync/upload? or during publish?
- Groomed changed from No to Yes
I was not able to find any old repos where the epoch is an empty string.
- Subject changed from package without epoch in the erratum pkglist is not handled correctly during publish to fixtures repo is missing 'epoch' in the erratum pkglist
- Triaged changed from No to Yes
We should fix the fixtures repository as part of this issue
- Subject changed from fixtures repo is missing 'epoch' in the erratum pkglist to package without epoch in the erratum pkglist is not handled correctly during publish
- Status changed from NEW to POST
- Assignee set to ttereshc
- Has duplicate Issue #2217: updateinfo.xml is not generated with any packages added
- Related to Issue #833: older errata units may have 'null' in database for pkglist package epoch added
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Platform Release set to 2.9.3
- Sprint/Milestone set to 25
- Status changed from MODIFIED to 5
- Status changed from 5 to 6
- Status changed from 6 to CLOSED - CURRENTRELEASE
- Sprint/Milestone deleted (
25)
Also available in: Atom
PDF
.
Fix package filtering for errata when no epoch is specified
closes #1926 https://pulp.plan.io/issues/1926