https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-08-30T12:09:41ZPulpPulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=217472017-08-30T12:09:41Zdemter@atix.deklaas@demter.de
<ul></ul><p>well other way around -- first one is the old one; 2nd erratum is the new one</p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=217482017-08-30T12:22:22Zttereshcttereshc@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/21748/diff?detail_id=22256">diff</a>)</li></ul><p>Fixed description, as per comment 1.</p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=217512017-08-30T13:02:35Zjsherril@redhat.comjsherril@redhat.com
<ul></ul><p>To summarize, after an IRC conversation. It seems that if an errata is updated and new errata packages are added (and the updated date is properly updated), pulp will import the errata properly. However if this is the only change to the repository (no rpms are actually added/removed), pulp seems to think that the repo publish does not need to occur via the 'auto_publish' setting on the repository and won't publish those changes. A force_full publish seems to resolve it.</p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=217692017-09-01T16:10:55Zttereshcttereshc@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=217702017-09-01T16:12:40Zttereshcttereshc@redhat.com
<ul><li><strong>Sprint Candidate</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=219552017-09-21T14:19:14Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> set to <i>45</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=222262017-10-04T13:06:26Zttereshcttereshc@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>ttereshc</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=222742017-10-06T12:23:31Zttereshcttereshc@redhat.com
<ul><li><strong>Subject</strong> changed from <i>Erratum not updated after upstream change</i> to <i>Publish is no-op for repos which contain unit updated by sync of the other repo</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/22274/diff?detail_id=22745">diff</a>)</li></ul><p>I was not able to reproduce the issue as described. Publish is operational even if an erratum is the only change in the upstream repo.<br>
However I found out that such issue can happen to the copies of repositories. <del>And it happens not only for errata but for any unit.</del> In case of RPM repo it happens for errata only.<br>
Say, erratum <del>or rpm</del> was updated upstream, a repo with a feed was synced again. The fact that something changed is visible only for the repo which was synced and it's not noticeable for the copies of repo which contain the same unit.<br>
So for repo with a feed - publish will be operational, but for repo copies - publish will be no-op and force_full option should be used.</p>
<p>I'm changing title accordingly, let me know if anyone disagrees.</p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=222752017-10-06T12:25:06Zttereshcttereshc@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/3183" class="external">https://github.com/pulp/pulp/pull/3183</a></p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=224422017-10-18T15:28:28Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>45</i> to <i>46</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=227572017-11-06T13:11:05Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Sprint/Milestone</strong> changed from <i>46</i> to <i>47</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=231002017-11-30T20:59:11Zrchan
<ul><li><strong>Sprint/Milestone</strong> changed from <i>47</i> to <i>48</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=231612017-12-03T13:15:01Zttereshcttereshc@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>CLOSED - WONTFIX</i></li></ul><p>The proposed fix has substantial impact on sync/publish performance in certain cases. The issue itself (no-op publish in copies of the repo if an erratum update is the only change) will be solved automatically with the next changes to the affected repository copies, or it can be overcome using force_full publish.</p> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=263112018-03-08T23:28:24Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 29</i></li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=263202018-03-08T23:28:54Zbmbouterbmbouter@redhat.com
<ul><li><strong>Sprint/Milestone</strong> deleted (<del><i>48</i></del>)</li></ul> Pulp - Issue #2994: Publish is no-op for repos which contain unit updated by sync of the other repohttps://pulp.plan.io/issues/2994?journal_id=381542019-04-15T20:16:03Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>