https://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-01-10T11:30:13ZPulpRPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=517872020-01-10T11:30:13Zipanova@redhat.comipanova@redhat.com
<ul></ul><p>In Pulp2 errata is the only mutable content and publish does not check on that. The fix would be much more invasive than using the workaround and likely will have an impact on the performance. The workaround would be to trigger force_full publish. It will regenerate metadata from scratch and contain the updates performed on the errata. I do not foresee it fixed in Pulp2 being in maintenance mode.</p>
<p>There won't be such problem in Pulp 3.</p> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=518732020-01-14T05:45:46Zrmcgoverrmcgover@redhat.com
<ul></ul><p>I'd like to point out that the workarounds probably are not as simple as it might seem at first glance:</p>
<p>For the force_full suggestion, we need to minimize the number of force_full publishes triggered because they can be extremely slow for large repos.</p>
<p>For the other workaround I mentioned in the report - upload the changed erratum to every repo containing it - the naive implementation would be "when updating an advisory, check the repos containing the advisory, then upload to each of them". However, that wouldn't be robust against being interrupted/cancelled and retried. If it were interrupted part way through the uploads and then retried, the advisory would already be up-to-date on the next attempt, so the needed uploads wouldn't be triggered. To be robust, the client will have to do unnecessary upload requests even when an advisory is already up-to-date or will have to add extra code to explicitly compare last_unit_added against the erratum timestamp on each repo.</p>
<p>As such, before committing to working around this in the clients I'd probably at least try a Pulp patch first.</p> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=522572020-01-22T01:36:03Zrmcgoverrmcgover@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>POST</i></li><li><strong>Assignee</strong> set to <i>rmcgover</i></li></ul><p>Pull requests for review: <a href="https://github.com/pulp/pulp/pull/3973" class="external">https://github.com/pulp/pulp/pull/3973</a>, <a href="https://github.com/pulp/pulp_rpm/pull/1584" class="external">https://github.com/pulp/pulp_rpm/pull/1584</a>.</p> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=522592020-01-22T09:23:31Zppicka
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=523982020-01-23T17:19:48Zrmcgoverrmcgover@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="Ensure updating erratum sets last_unit_added on *all* repos When we update an erratum, this affe..." href="https://pulp.plan.io/projects/pulp_rpm/repository/9/revisions/69759d0fb9a16c0a47b1f49c78f6712e650912e1">69759d0fb9a16c0a47b1f49c78f6712e650912e1</a>.</p> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=531422020-02-18T11:19:24Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/53142/diff?detail_id=53569">diff</a>)</li><li><strong>Platform Release</strong> set to <i>2.21.1</i></li></ul> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=533982020-02-25T13:33:35Zrmcgoverrmcgover@redhat.com
<ul></ul><p>Applied in changeset <a class="changeset" title="Ensure updating erratum sets last_unit_added on *all* repos When we update an erratum, this affe..." href="https://pulp.plan.io/projects/pulp_rpm/repository/9/revisions/6fa51aabf719507759636761e2c4f33f54d741f9">6fa51aabf719507759636761e2c4f33f54d741f9</a>.</p> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=535292020-02-27T16:38:39Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> RPM Support - Issue #5951: yum_distributor wrongly skips publish after update of multi-repo erratahttps://pulp.plan.io/issues/5951?journal_id=537462020-03-04T16:46:42Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>