Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2018-09-24T20:35:08ZPulp
Planio Pulp - Test #4035 (CLOSED - COMPLETE): Test base_version parameterhttps://pulp.plan.io/issues/40352018-09-24T20:35:08Zdaviddavis
<p>In <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: As a user, I can create a repository version from any repository version (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/3360">#3360</a>, we introduced a new param to the POST /pulp/api/v3/repositories/1/versions/ call that lets you set the base repository version. This lets users copy the contents of one repository into another.</p>
<a name="Test-same-repository"></a>
<h2 >Test same repository<a href="#Test-same-repository" class="wiki-anchor">¶</a></h2>
<p>1. Create a new repo<br>
2. Sync the repo (this creates repo version 1)<br>
3. Upload (or associate) a new content unit a new repository version (this create repo version 2)<br>
4. Create a new repo version from version 1 (this creates version 3)<br>
5. Check that version 1 and version 3 have the same content</p>
<a name="Test-different-repository"></a>
<h2 >Test different repository<a href="#Test-different-repository" class="wiki-anchor">¶</a></h2>
<p>1. Create a new repo A and sync it<br>
2. Create a new repo B and a new version for this repo specify repo A version 1 as the base_version<br>
3. Check that repo A version 1 and repo B version 2 have the same content</p> Pulp - Task #4003 (CLOSED - WONTFIX): Uncouple pulpcore tests from plugins by creating a test pluginhttps://pulp.plan.io/issues/40032018-09-12T14:29:02Zdaviddavis
<p>Some of pulpcore tests rely on the pulp_file[0] and pulp_rpm[1] plugins. The problem is that this won't scale. As we add more features to pulpcore that are only used by a subset of plugins, this design will require us to install more plugins into pulpcore's CI.</p>
<p>We should decouple pulpcore tests from requiring plugins by introducing a test plugin that tests can use. This test plugin would contain a superset of all features that pulpcore provides.</p>
<p>Alternatively we could maybe leverage the plugin template to be this test plugin.</p>
<p>[0] <a href="https://github.com/pulp/pulpcore/tree/master/pulpcore/tests/functional/api/using_plugin" class="external">https://github.com/pulp/pulpcore/tree/master/pulpcore/tests/functional/api/using_plugin</a><br>
[1] <a href="https://github.com/pulp/pulpcore/blob/master/pulpcore/tests/functional/api/using_plugin/test_sync_multiple_plugins.py" class="external">https://github.com/pulp/pulpcore/blob/master/pulpcore/tests/functional/api/using_plugin/test_sync_multiple_plugins.py</a></p> Debian Support - Issue #3928 (CLOSED - NOTABUG): support multiple repos/relases with same feedhttps://pulp.plan.io/issues/39282018-08-21T15:01:54Zd.noorman@flexyz.com
<p>added first:<br>
pulp-admin deb repo create --repo-id 'trusty' --feed '<a href="http://nl.archive.ubuntu.com/ubuntu" class="external">http://nl.archive.ubuntu.com/ubuntu</a>' --releases 'trusty' --components 'security' --architectures 'amd64'</p>
<p>addec second:<br>
pulp-admin deb repo create --repo-id 'bionic-security-amd64' --feed '<a href="http://nl.archive.ubuntu.com/ubuntu" class="external">http://nl.archive.ubuntu.com/ubuntu</a>' --releases 'bionic' --components 'security' --architectures 'amd64'</p>
<p>Error<br>
Relative URL [ubuntu] for repository [bionic-security-amd64] conflicts with<br>
existing relative URL [/ubuntu] for repository [xenial-amd64]</p> Pulp - Story #3576 (CLOSED - CURRENTRELEASE): As a user, I know that publications are ordered by ...https://pulp.plan.io/issues/35762018-04-18T14:01:54Zdkliban@redhat.comRPM Support - Story #3204 (CLOSED - CURRENTRELEASE): As a user, I can publish RPM/Erratum in a wa...https://pulp.plan.io/issues/32042017-12-14T19:13:32Zttereshcttereshc@redhat.com
<p>As a user, I can publish RPM/Erratum in a way that is consumable by yum/dnf.</p>
<p>Use createrepo_c to generate all the necessary metadata.</p>
<p>This story is complete when:</p>
<ul>
<li>The publication creation completes without error</li>
<li>I can use yum/dnf to install or list packages from the repo</li>
<li>I can use yum/dnf to install or list errata from the repo</li>
</ul> Pulp - Story #2659 (CLOSED - CURRENTRELEASE): As a User I would like Pulp3 to not show me offline...https://pulp.plan.io/issues/26592017-03-23T18:28:18Zbizhangbizhang@redhat.com
<p>Assumption: Pulp workers that are missing should not be shown in the status API.</p>
<p>In Pulp3, the Worker model has an 'online' boolean which is meant to allow Pulp to store records about workers even after they have gone offline. Additionally workers should be considered offline if their heartbeat time is older than 30 seconds. We need to filter for both cases because of the following failure scenario:</p>
<p>1) a working Pulp system with exactly 1 worker that has pid 1234<br>
2) kill -9 1234</p>
<p>In this case, the DB record will show 'online' without the 30 second part of the filter.</p>
<p>To resolve this we should:</p>
<p>1) add a method called <code>online_workers</code> to the <a href="https://github.com/bmbouter/pulp/blob/e5986173d1617fcadb520c84b78691982cce2218/platform/pulpcore/app/models/task.py#L38" class="external">TaskManager</a> which returns a queryset with the two filters applied as described above<br>
2) refactor the <a href="https://github.com/bmbouter/pulp/blob/e5986173d1617fcadb520c84b78691982cce2218/platform/pulpcore/app/models/task.py#L40" class="external">get_unreserved_worker</a> method to use <code>online_workers</code> instead. This will cause us to stay DRY w.r.t. this filtering.<br>
3) Have the ViewSet of the /status/ API only return workers from the <code>online_workers</code> queryset.<br>
4) Update the docstrings so that those updates will flow to the docs</p>