Project

Profile

Help

Issue #1926

closed

package without epoch in the erratum pkglist is not handled correctly during publish

Added by ttereshc almost 8 years ago. Updated almost 5 years ago.

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

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.


Related issues

Related to RPM Support - Issue #833: older errata units may have 'null' in database for pkglist package epochCLOSED - CURRENTRELEASEcduryeeActions
Has duplicate RPM Support - Issue #2217: updateinfo.xml is not generated with any packagesCLOSED - DUPLICATEActions

Also available in: Atom PDF