Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2022-01-12T15:43:50ZPulp
Planio Pulp - Backport #9668 (CLOSED - CURRENTRELEASE): Backport #9665: Make the `adjust_roles` function...https://pulp.plan.io/issues/96682022-01-12T15:43:50Zdkliban@redhat.com
<p>While migrating to the Roles backend I find I need to access <code>adjust_roles</code> [1] and CI throws an error when accessing it via <code>from pulpcore.app.apps import adjust_roles</code> [2].</p>
<p>[1] <a href="https://github.com/pulp/pulpcore/blob/main/pulpcore/app/apps.py#L269" class="external">https://github.com/pulp/pulpcore/blob/main/pulpcore/app/apps.py#L269</a>
[2] <a href="https://github.com/ansible/galaxy_ng/runs/4731797454?check_suite_focus=true" class="external">https://github.com/ansible/galaxy_ng/runs/4731797454?check_suite_focus=true</a></p> Pulp - Backport #9664 (CLOSED - CURRENTRELEASE): Backport #9660 "django update broke pulpimport f...https://pulp.plan.io/issues/96642022-01-06T17:54:23Zttereshcttereshc@redhat.com
<p>Django addressed a security issue involving filepaths in a way that broke how pulpimport was using Storage:</p>
<p>In 3.14, the following failure in <code>pulp_rpm.tests.functional.api.test_pulpimport.ParallelImportTestCase testMethod=test_clean_import</code> :</p>
<pre><code class="text syntaxhl" data-language="text">E pulp_smash.pulp3.bindings.PulpTaskError: (PulpTaskError(...), "Pulp task failed (Detected path traversal attempt in '/var/lib/pulp/media/artifact/d4/89a5ea552e5ea595976e39f891fe249e95d8eb40cbd7f50a46c0126a7072ab')")
</code></pre>
<p>Against core/main, the same test hangs.</p>
<p>The problem is that core/import builds a full-path to send to Storage.save(), which used to "work" but is now Not Allowed (for perfectly good security-reasons)</p>
<p>See <a href="https://github.com/pulp/pulpcore/blob/main/pulpcore/app/tasks/importer.py#L396" class="external">https://github.com/pulp/pulpcore/blob/main/pulpcore/app/tasks/importer.py#L396</a></p> Pulp - Issue #9654 (CLOSED - CURRENTRELEASE): backport 9642 to 3.17.1: Migration 081 was incompat...https://pulp.plan.io/issues/96542021-12-21T15:05:31Zdkliban@redhat.comRPM Support - Issue #9627 (MODIFIED): publish fails on MD5-checksummed repos, on FIPShttps://pulp.plan.io/issues/96272021-12-09T18:59:35Zggainey
<p>See associated BZ for details, reproducer</p> RPM Support - Test #9622 (MODIFIED): Add a repo signed using 'sha' as alias for 'sha1'https://pulp.plan.io/issues/96222021-12-08T19:00:00Zggainey
<p>'sha' support exists in the wild, is the same as 'sha1', and has broken us several times now, Let's make it possible to write tests for it.</p> Pulp - Story #9621 (CLOSED - CURRENTRELEASE): As a user I can pass environment variables to the s...https://pulp.plan.io/issues/96212021-12-08T18:14:33Zipanova@redhat.comipanova@redhat.comContainer Support - Task #9618 (CLOSED - CURRENTRELEASE): Adjust code to work wiht recent group p...https://pulp.plan.io/issues/96182021-12-08T16:34:14ZmdellwegMigration Plugin - Backport #9612 (MODIFIED): Backport #8968 "'NoneType' object has no attribute ...https://pulp.plan.io/issues/96122021-12-07T18:13:47Zttereshcttereshc@redhat.com
<p>Backtrace:</p>
<pre>
"error"=>
{"traceback"=>
" File \"/usr/lib/python3.6/site-packages/rq/worker.py\", line 936, in perform_job\n" +
" rv = job.perform()\n" +
" File \"/usr/lib/python3.6/site-packages/rq/job.py\", line 684, in perform\n" +
" self._result = self._execute()\n" +
" File \"/usr/lib/python3.6/site-packages/rq/job.py\", line 690, in _execute\n" +
" return self.func(*self.args, **self.kwargs)\n" +
" File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/tasks/migrate.py\", line 76, in migrate_from_pulp2\n" +
" pre_migrate_all_without_content(plan)\n" +
" File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/pre_migration.py\", line 493, in pre_migrate_all_without_content\n" +
" pre_migrate_importer(repo_id, importer_types)\n" +
" File \"/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/pre_migration.py\", line 601, in pre_migrate_importer\n" +
" importer.pulp3_remote.delete()\n",
"description"=>"'NoneType' object has no attribute 'delete'"},
"worker"=>"/pulp/api/v3/workers/fc6ba1d6-ddc6-494d-9385-2368544a09ef/",
</pre>
<p>This happened on Katello 3.18.3 which uses:</p>
<pre>
pulp-2to3-migration (0.11.1)
pulp-certguard (1.0.3)
pulp-container (2.1.2)
pulp-deb (2.7.0)
pulp-file (1.3.0)
pulp-rpm (3.10.0)
pulpcore (3.7.6)
</pre> Container Support - Backport #9610 (CLOSED - CURRENTRELEASE): backport to 2.8: Enable rate_limit ...https://pulp.plan.io/issues/96102021-12-07T17:23:31Zipanova@redhat.comipanova@redhat.com
<p><a href="https://pulp.plan.io/issues/9607" class="external">https://pulp.plan.io/issues/9607</a></p> Pulp - Issue #9608 (CLOSED - CURRENTRELEASE): Deprecation warning in Roles doesn't include enough...https://pulp.plan.io/issues/96082021-12-06T20:16:41Zbmbouterbmbouter@redhat.com
<p>When running pclean (or a user at upgrade time) on <code>pulp:main</code> would see this warning:</p>
<p><code>pulp [None]: pulpcore.deprecation:WARNING: The 'permissions' field in 'creation_hooks' is deprecated and may be removed with pulpcore 3.20. Use the 'parameters' field instead.</code></p>
<p>This is telling us that we haven't ported the AcessPolicy for ContentGuard, except that it doesn't indicate that it's about ContentGuard. These messages should be improved.</p> Pulp - Story #9606 (CLOSED - CURRENTRELEASE): As a user who manages permissions, I can reset an a...https://pulp.plan.io/issues/96062021-12-06T15:40:13Zbmbouterbmbouter@redhat.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Users can modify access policies, but sometimes they may want to reset it back to the shipped default.</p>
<a name="Design"></a>
<h2 >Design<a href="#Design" class="wiki-anchor">¶</a></h2>
<p>The detail view of an AccessPolicy should have a <code><path_to_AccessPolicy_instance>/reset/</code> endpoint that accepts a POST. Upon posting it should:</p>
<ol>
<li>Restore the default access policy</li>
<li>Ensure that the customized flag is false</li>
</ol> Container Support - Backport #9601 (CLOSED - CURRENTRELEASE): Backport 9586 to pulp_container 2.8https://pulp.plan.io/issues/96012021-12-02T20:23:02Znewswangerd
<p>We'd like to request that 9586 be backported to pulp_container 2.8 so that it can be used in galaxy_ng 4.4</p> Container Support - Backport #9600 (CLOSED - CURRENTRELEASE): Backport 9586 to pulp_container 2.5https://pulp.plan.io/issues/96002021-12-02T20:22:29Znewswangerd
<p>We'd like to request that 9586 be backported to pulp_container 2.5 so that it can be used in galaxy_ng 4.3</p> Pulp - Issue #9590 (MODIFIED): Pulp CI badges are no longer validhttps://pulp.plan.io/issues/95902021-11-30T15:50:22Zlmjachky
<p>Current Pulp CI status badges are no longer valid after merging the commit <a href="https://github.com/pulp/pulpcore/commit/dae72fa404de50b347d877c89c1a269937ab27b0#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fL13-L15" class="external">https://github.com/pulp/pulpcore/commit/dae72fa404de50b347d877c89c1a269937ab27b0#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fL13-L15</a> (we did not want to run the CI pipeline once again after merging changes).</p>
<p>Removing status badges from all repositories should be sufficient to resolve the problem. Having only Pulp Nightly CI/CD badges available is good enough (<a href="https://github.com/pulp/pulp-ci" class="external">https://github.com/pulp/pulp-ci</a>).</p> Maven Plugin - Issue #8678 (MODIFIED): Provide 'view_name' warning when using the all in one cont...https://pulp.plan.io/issues/86782021-04-30T19:17:03Zgerrod
<p>A user from pulp-dev was worried about this warning message appearing after changing the admin password to the all in one container. Pretty sure it's harmless, but it can scare users thinking that their installation isn't correct.</p>
<p><code>pulpcore.app.serializers.base:WARNING: Please provide either 'view_name' or 'view_name_pattern' for DetailRelatedField on _call_with_frames_removed.</code></p>