Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-12-12T06:09:47ZPulp
Planio RPM Support - Task #9633 (CLOSED - DUPLICATE): Use repo priorities in the dependency solverhttps://pulp.plan.io/issues/96332021-12-12T06:09:47Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2309":<a href="https://github.com/pulp/pulp_rpm/issues/2309" class="external">https://github.com/pulp/pulp_rpm/issues/2309</a></p>
<hr>
<p>We ought to be setting repo priorities such that for every set of copies, any matching RPMs present in the same repository are prioritzed over ones in other repos.</p> RPM Support - Task #9585 (CLOSED - DUPLICATE): Sub-tree-only sync breaks our model of how syncs a...https://pulp.plan.io/issues/95852021-11-23T21:00:08Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2306":<a href="https://github.com/pulp/pulp_rpm/issues/2306" class="external">https://github.com/pulp/pulp_rpm/issues/2306</a></p>
<hr>
<p>See: <a href="https://pulp.plan.io/issues/9565" class="external">https://pulp.plan.io/issues/9565</a></p>
<p>We haven't considered the possibility of a repository having a .treeinfo but no top-level repodata. We need to investigate whether this breaks anything (for example: autopublish), and potentially add a new test fixture to exercise it.</p> Container Support - Task #9572 (CLOSED - DUPLICATE): Port the RBAC implementation to the pulpcore...https://pulp.plan.io/issues/95722021-11-16T13:48:53Zmdellweg
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/508":<a href="https://github.com/pulp/pulp_container/issues/508" class="external">https://github.com/pulp/pulp_container/issues/508</a></p>
<hr>
<p>Start with a PoC PR to get the pulpcore PR merged first.</p>
<p>Once that is done, we need to write a data migration that will look for the autogenerated groups and translate them into user_object_roles.
To be discussed: Look if we can be clever with global permissions too.</p> Pulp - Task #9569 (CLOSED - DUPLICATE): Eliminate all instances when Pulp writes to /tmp and alwa...https://pulp.plan.io/issues/95692021-11-15T19:13:19Zttereshcttereshc@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2061":<a href="https://github.com/pulp/pulpcore/issues/2061" class="external">https://github.com/pulp/pulpcore/issues/2061</a></p>
<hr>
<p>There were various issues due to Pulp writing to /tmp, mostly it's running out of disc space because /tmp is usually not expected to be large.<br>
Problems come from <code>NamedTemporaryFile</code> and <code>TemporaryDirectory</code> which do not have <code>dir</code> parameter specified.</p>
<p>There is also inconsistency in how directories are referred to.<br>
Let's fix it as well.<br>
Current flavours for the current directory are <code>dir="."</code> and <code>dir=os.getcwd()</code>.</p>
<p>It would be good to check plugins as well, I just fixed 4 places in pulp_rpm.</p> Migration Plugin - Task #9517 (CLOSED - CURRENTRELEASE): Specify SigningService in migration-planhttps://pulp.plan.io/issues/95172021-10-18T16:05:00Zmbucher
<p>It should be possible to specify the name of an existing SigningService instance for a (deb-)repository in the complex migration-plan.</p>
<p>This ensures that the migrated repository will already be correctly signed, which is important for APT-repositories to be accepted by the apt package-manager.</p>
<p>This <em>does not include</em> migrating any pre-existing signing-script and key into a pulpcore SigningService.</p> Pulp - Task #9501 (CLOSED - DUPLICATE): Mention upload objects are only for in progress uploadshttps://pulp.plan.io/issues/95012021-10-11T15:35:20Zgerrod
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2060":<a href="https://github.com/pulp/pulpcore/issues/2060" class="external">https://github.com/pulp/pulpcore/issues/2060</a></p>
<hr>
<p>Docs should mention that the upload objects are for current file uploads happening in Pulp right now, and are subject to being deleted after the upload is complete.</p> Pulp - Task #9455 (CLOSED - DUPLICATE): Remove pulp-smash from pypihttps://pulp.plan.io/issues/94552021-09-28T12:03:21Zdaviddavis
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2056":<a href="https://github.com/pulp/pulpcore/issues/2056" class="external">https://github.com/pulp/pulpcore/issues/2056</a></p>
<hr>
<p>We should use pulp-smash from source instead of having to release it every time there's a change.</p>
<p>The one last place I know of that pulp-smash is used from PyPI is the Pulp-2-Tests. I opened a PR to fix this but the tests were failing:</p>
<p><a href="https://github.com/pulp/Pulp-2-Tests/pull/223" class="external">https://github.com/pulp/Pulp-2-Tests/pull/223</a></p> Pulp - Task #9418 (CLOSED - CURRENTRELEASE): expose pulpcore.app.tasks on pulpcore.plugin.taskshttps://pulp.plan.io/issues/94182021-09-16T17:24:46Zrochacbruno
<p>Plugin writers often need to call orphan_cleanup, general_removal, reclaim_space and other tasks from core.</p>
<p>Those tasks must be surfaced on plugin namespace.</p> Pulp - Task #9414 (CLOSED - DUPLICATE): remove django-guardian from the stackhttps://pulp.plan.io/issues/94142021-09-16T15:53:15Zmdellweg
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2051":<a href="https://github.com/pulp/pulpcore/issues/2051" class="external">https://github.com/pulp/pulpcore/issues/2051</a></p> Pulp - Task #9412 (CLOSED - DUPLICATE): Remove group permission endpointshttps://pulp.plan.io/issues/94122021-09-16T15:50:35Zmdellweg
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2050":<a href="https://github.com/pulp/pulpcore/issues/2050" class="external">https://github.com/pulp/pulpcore/issues/2050</a></p> Pulp - Task #9389 (CLOSED - DUPLICATE): Add a proxy testhttps://pulp.plan.io/issues/93892021-09-13T18:10:44Zdaviddavis
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2045":<a href="https://github.com/pulp/pulpcore/issues/2045" class="external">https://github.com/pulp/pulpcore/issues/2045</a></p>
<hr>
<p>This comes up from time to time: a product/plugin/user says that proxy support in Pulp is not working. It's usually a configuration problem.</p>
<p>It would be nice to have a test that sets up and uses a proxy in our CI to verify whether proxy support is working. I'm imagining that we could implement this in pulp_file but plugins could also extend this to test out any proxy-specific features they have or care about.</p>
<p>One promising lightweight option for setting up a proxy is <a href="https://github.com/abhinavsingh/proxy.py" class="external">proxy.py</a>.</p> Pulp - Task #9386 (CLOSED - CURRENTRELEASE): Ensure the installer no longer starts the resource m...https://pulp.plan.io/issues/93862021-09-13T13:43:06Zfao89File Support - Task #9341 (CLOSED - CURRENTRELEASE): Validate ACS pathshttps://pulp.plan.io/issues/93412021-09-02T16:30:20ZdaviddavisPulp - Task #9294 (CLOSED - CURRENTRELEASE): Enable all kube-linter ruleshttps://pulp.plan.io/issues/92942021-08-25T18:43:28Zfao89Pulp - Task #9256 (CLOSED - DUPLICATE): [EPIC] Use shared task resources in plugin codehttps://pulp.plan.io/issues/92562021-08-19T11:32:47Zmdellweg
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2041":<a href="https://github.com/pulp/pulpcore/issues/2041" class="external">https://github.com/pulp/pulpcore/issues/2041</a></p>