Pulp

02/25/2020

• 
  rmcgover RPM Support

  02:33 PM · Commented on issue

  Applied in changeset commit:6fa51aabf719507759636761e2c4f33f54d741f9. Issue #5951: yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  ## Steps to reproduce
  In summary: put...

02/24/2020

• 
  rmcgover Pulp

  11:45 AM · Committed changeset

  This is a follow-up to commits for issue #5951.
  Previous commits made it so that mutating an erratum unit would set
  last_unit_added on all affected repos; however, the code for deciding
  whether to skip publish ignored this field and only... Revision 617236a4 (pulp): Respect last_unit_added when deciding whether to publish
• 
  rmcgover Pulp

  11:45 AM · Committed changeset

  In rare cases where mutating a single unit can affect multiple
  repos at once (e.g. erratum units), it's necessary to set
  last_unit_added on all relevant repos. Add a controller method
  for this, to be invoked by the relevant importer(s).
  ... Revision 6b7272fd (pulp): Add controller method for multi-repo update of last_unit_added
• 
  rmcgover RPM Support

  11:42 AM · Committed changeset

  When we update an erratum, this affects not only the repo
  for which the update was requested, but also every other repo
  containing the same erratum.
  Therefore, rather than letting the controller only set
  last_unit_added on the specific ... Revision 6fa51aab: Ensure updating erratum sets last_unit_added on *all* repos

02/03/2020

• 
  rmcgover Pulp

  06:49 AM · Committed changeset

  This is a follow-up to commits for issue #5951.
  Previous commits made it so that mutating an erratum unit would set
  last_unit_added on all affected repos; however, the code for deciding
  whether to skip publish ignored this field and only... Revision d73366bd (pulp): Respect last_unit_added when deciding whether to publish

01/23/2020

• 
  rmcgover RPM Support

  06:19 PM · Closed issue

  Applied in changeset commit:69759d0fb9a16c0a47b1f49c78f6712e650912e1.
  Issue #5951 (MODIFIED): yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  ## Steps to reproduce
  In summary: put...
• 
  rmcgover RPM Support

  04:10 AM · Committed changeset

  When we update an erratum, this affects not only the repo
  for which the update was requested, but also every other repo
  containing the same erratum.
  Therefore, rather than letting the controller only set
  last_unit_added on the specific ... Revision 69759d0f: Ensure updating erratum sets last_unit_added on *all* repos

01/22/2020

• 
  rmcgover RPM Support

  02:36 AM · Edited issue

  Pull requests for review: https://github.com/pulp/pulp/pull/3973, https://github.com/pulp/pulp_rpm/pull/1584.
  Issue #5951 (POST): yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  ## Steps to reproduce
  In summary: put...
• 
  rmcgover Pulp

  02:23 AM · Committed changeset

  In rare cases where mutating a single unit can affect multiple
  repos at once (e.g. erratum units), it's necessary to set
  last_unit_added on all relevant repos. Add a controller method
  for this, to be invoked by the relevant importer(s).
  ... Revision 94986211 (pulp): Add controller method for multi-repo update of last_unit_added

01/14/2020

• 
  rmcgover RPM Support

  06:45 AM · Commented on issue

  I'd like to point out that the workarounds probably are not as simple as it might seem at first glance:
  For the force_full suggestion, we need to minimize the number of force_full publishes triggered because they can be extremely slow f... Issue #5951: yum_distributor wrongly skips publish after update of multi-repo errata

  When multi-repo errata are used, publishing a repo may skip with "Repository content has not changed since last publish", even if erratum units in the repo have been changed since last publish.
  ## Steps to reproduce
  In summary: put...