https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-05-12T21:07:19ZPulpRPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=706992021-05-12T21:07:19Zdalleydalley@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-12 priority-6 priority-default closed parent" href="/issues/8740">Task #8740</a>: [EPIC] Publication based plugins should use either `distribution.repository` or `distribution.publication` but not both</i> added</li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=707142021-05-13T13:38:42Zdalleydalley@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-11 priority-6 priority-default closed" href="/issues/6353">Story #6353</a>: As a user, I can mirror RPM repository content and metadata</i> added</li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=707162021-05-13T13:40:51Zdalleydalley@redhat.com
<ul></ul><p><a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: As a user, I can mirror RPM repository content and metadata (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/6353">#6353</a> should help with this, since metadata mirroring avoids the need for a publishing step - even via auto-publishing.</p>
<p>Although of course for custom repos, auto-publish is necessary to make repo modifications convenient.</p> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=714402021-05-27T02:49:45Zdalleydalley@redhat.com
<ul></ul><p>@sskracic I would call this "an expected but unfortunate corner case". In this situation, which would you prefer to happen?</p>
<ul>
<li>The current behavior (with maybe some additional logging of warnings)</li>
<li>Have entire task fail and all changes reverted, including the destruction of the repository version that was created. This means that the operation that created the repository version would need to be re-done in its entirety.</li>
</ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=714542021-05-27T13:20:18Zsskracic@redhat.comsskracic@redhat.com
<ul></ul><p>dalley wrote:</p>
<blockquote>
<p>@sskracic I would call this "an expected but unfortunate corner case". In this situation, which would you prefer to happen?</p>
<ul>
<li>The current behavior (with maybe some additional logging of warnings)</li>
<li>Have entire task fail and all changes reverted, including the destruction of the repository version that was created. This means that the operation that created the repository version would need to be re-done in its entirety.</li>
</ul>
</blockquote>
<p>If feasible, I would prefer the latter. My understanding is that with the artifacts already being downloaded, only their associations to the new repo version will need to be redone on the next sync run.</p> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=735602021-07-21T19:41:45Zdalleydalley@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 101</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=740882021-08-02T17:44:22Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Sprint</strong> changed from <i>Sprint 101</i> to <i>Sprint 102</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=744682021-08-12T15:23:46Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 102</i> to <i>Sprint 103</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=749802021-08-27T15:08:04Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 103</i> to <i>Sprint 104</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=754112021-09-09T22:28:12Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 104</i> to <i>Sprint 105</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=755022021-09-11T02:30:37Zdalleydalley@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=759122021-09-23T21:54:41Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 105</i> to <i>Sprint 106</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=764352021-10-08T13:16:05Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 106</i> to <i>Sprint 107</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=767192021-10-21T16:35:39Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 107</i> to <i>Sprint 108</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=770012021-11-04T21:21:49Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 108</i> to <i>Sprint 109</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=772682021-11-19T20:39:36Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 109</i> to <i>Sprint 110</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=775052021-12-03T22:00:39Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 110</i> to <i>Sprint 111</i></li></ul> RPM Support - Story #8673: Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/8673?journal_id=780612021-12-22T15:32:47Zpulpbot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/78061/diff?detail_id=78642">diff</a>)</li><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul>