Advisory package list doesn't match packages in the repository
We have following situation, which is quite common in our releasing process:
Async errata contains multiple products and set of all packages for these products. Advisory is pushed into repositories related to the products and selected subset of packages from advisory is uploaded to the repository. However after after yum publish, generated updateinfo contains advisory with all packages even with those that are not in the repository. Therefore we need filter out packages of advisory that are not in the repository.
published updateinfo only contains units in repo
Errata units in Pulp contain all units in all repos that are linked to errata with the same id, which was resulting in published errata referencing packages that weren't actually available in the published repo. This limits packages in published errata updateinfo XML to only the packages that are contained in the published repo.
#3 Updated by jluza over 4 years ago
- Version changed from 2.5 to 2.7.1
suggested change at
- it would be definitely better to have some rewindable generator than have as_generator=False
- it would be better to query packages just for filename field, however I'm not sure if it's possible.
#8 Updated by semyers over 4 years ago
Each issue is related to a different downstream bugzilla issue, so I'm keeping them both open and will ref them both in my commit message. I've linked the issues in Redmine, marking this one as the duplicate. My comments and progress can be followed over on #1548.
Please register to edit this issue