Project

Profile

Help

Issue #1366

closed

Advisory package list doesn't match packages in the repository

Added by jluza over 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.7.1
Platform Release:
2.8.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

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.


Related issues

Has duplicate RPM Support - Issue #1548: published errata contain packages not in repoCLOSED - CURRENTRELEASEsemyersActions
Actions #1

Updated by mhrivnak over 8 years ago

  • Priority changed from Normal to High
  • Triaged changed from No to Yes
Actions #3

Updated by jluza about 8 years ago

  • Version changed from 2.5 to 2.7.1

suggested change at
https://github.com/release-engineering/pulp_rpm/commits/2.7-dev-%231366

Few notes:
- 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.

Actions #4

Updated by mhrivnak about 8 years ago

  • Platform Release set to 2.8.1
Actions #5

Updated by mhrivnak about 8 years ago

There is a bit of similar functionality in the yum profiler. See pulp_rpm.plugins.profilers.yum.YumProfiler. Specifically the _get_rpms_from_errata and _translate_erratum functions.

Actions #6

Updated by mhrivnak about 8 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to semyers

This looks like a duplicate of #1548. I'll let semyers confirm and decide which to close.

Actions #7

Updated by semyers about 8 years ago

  • Has duplicate Issue #1548: published errata contain packages not in repo added
Actions #8

Updated by semyers about 8 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.

Actions #9

Updated by bmbouter about 8 years ago

  • Parent issue set to #1683
Actions #10

Updated by semyers about 8 years ago

  • Status changed from ASSIGNED to POST

Added by semyers about 8 years ago

Revision 73d67dd4 | View on GitHub

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.

fixes #1366 https://pulp.plan.io/issues/1366

fixes #1548 https://pulp.plan.io/issues/1548

Actions #11

Updated by semyers about 8 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #12

Updated by semyers about 8 years ago

  • Status changed from MODIFIED to 5
Actions #13

Updated by pthomas@redhat.com about 8 years ago

  • Status changed from 5 to 6

verified

[root@ibm-x3550m3-10 ~]# rpm -qa |grep pulp-server
pulp-server-2.8.1-0.1.beta.el7.noarch

Actions #14

Updated by semyers about 8 years ago

  • Status changed from 6 to CLOSED - CURRENTRELEASE
Actions #16

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF