Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-05-24T19:54:30ZPulp
Planio RPM Support - Test #8809 (CLOSED - DUPLICATE): Better tests for metadata mirroringhttps://pulp.plan.io/issues/88092021-05-24T19:54:30Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2277":<a href="https://github.com/pulp/pulp_rpm/issues/2277" class="external">https://github.com/pulp/pulp_rpm/issues/2277</a></p>
<hr>
<p>We need a fixture repository with some of the extra files, such as repomd.xml.asc (metadata signature), extra_files.json, .treeinfo, possibly licenses, multiple package directories / package locations, extra repomd entries that Pulp doesn't natively care about, etc. And then we need to test that mirroring works properly with such repos.</p> RPM Support - Story #8673 (CLOSED - DUPLICATE): Auto-publishing should be more fault-toleranthttps://pulp.plan.io/issues/86732021-04-30T14:56:08Zsskracic@redhat.comsskracic@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2273":<a href="https://github.com/pulp/pulp_rpm/issues/2273" class="external">https://github.com/pulp/pulp_rpm/issues/2273</a></p>
<hr>
<p>I admit the title is a bit vague.</p>
<p>During auto-publishing sync of a very large repository (rhel-7-server-rpms), the <code>rq</code> process got killed by oom-killer sometime in the middle of the publishing step. So the new repository version (1) got created, but accompanying
publication did not.</p>
<p>On the subsequent sync runs, the repository did not get published, as no new content was available to sync, hence a new repository version was not created, which in turn should trigger publication and distribution update.</p>
<p>Of course, the repo can still be published and distributed using the non-autopublishing REST API, but I wonder whether the behavior was intended.</p> Debian Support - Task #8643 (CLOSED - DUPLICATE): Rework the API docshttps://pulp.plan.io/issues/86432021-04-28T07:07:15Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/405":<a href="https://github.com/pulp/pulp_deb/issues/405" class="external">https://github.com/pulp/pulp_deb/issues/405</a></p>
<hr>
<p>I would like to systematically go through the strings used for the API docs, to ensure they provide all the critical information for users.</p> Debian Support - Task #8641 (CLOSED - DUPLICATE): Review handling of ALLOWED_CONTENT_CHECKSUMS in...https://pulp.plan.io/issues/86412021-04-28T07:02:46Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/403":<a href="https://github.com/pulp/pulp_deb/issues/403" class="external">https://github.com/pulp/pulp_deb/issues/403</a></p>
<hr>
<p>Right now we are testing using checksum settings that are not what most production setups will use.
The current settings also require manual intervention in devel boxes to run tests locally.</p>
<p>Ideally we would have different tests using different settings for full coverage.</p> RPM Support - Test #8335 (CLOSED - DUPLICATE): Need a new fixture - advisory, same date/version, ...https://pulp.plan.io/issues/83352021-03-03T20:04:27Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2268":<a href="https://github.com/pulp/pulp_rpm/issues/2268" class="external">https://github.com/pulp/pulp_rpm/issues/2268</a></p>
<hr>
<p><a href="https://pulp.plan.io/issues/8249" class="external">https://pulp.plan.io/issues/8249</a> changed the failure-case in advisory.resolve_advisory_conflict - need a fixture to reflect the failure-case, and an update to test_sync.py to re-enable test_sync_advisory_incomplete_pgk_list</p> Pulp - Task #8226 (CLOSED - CURRENTRELEASE): Remove # coding=utf-8 from plugin-templatehttps://pulp.plan.io/issues/82262021-02-08T18:18:29Zggainey
<p>Python3 defaults to utf8 now.</p> File Support - Task #8225 (CLOSED - DUPLICATE): Remove # coding=utf-8 from our testshttps://pulp.plan.io/issues/82252021-02-08T16:37:04Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_file/627":<a href="https://github.com/pulp/pulp_file/issues/627" class="external">https://github.com/pulp/pulp_file/issues/627</a></p>
<hr>
<p>Python3 defaults to utf8 now.</p> Pulp - Task #7908 (CLOSED - CURRENTRELEASE): Make sure all exceptions live in pulpcore.plugin.exc...https://pulp.plan.io/issues/79082020-12-01T13:38:59Zggainey
<p>See discussion at <a href="https://github.com/pulp/pulpcore/pull/1027#discussion_r524551412" class="external">https://github.com/pulp/pulpcore/pull/1027#discussion_r524551412</a></p>
<p>This will require a deprecation cycle, with a given exception living "in two places" for one release. Once this issue is in MODIFIED, open a new issue to complete the move.</p> Pulp - Task #7501 (CLOSED - DUPLICATE): Improve travis log output on migration-failureshttps://pulp.plan.io/issues/75012020-09-11T20:40:49Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1934":<a href="https://github.com/pulp/pulpcore/issues/1934" class="external">https://github.com/pulp/pulpcore/issues/1934</a></p>
<hr>
<p>If a migration conflicts with one, the resulting failures in travis are...opaque. To whit:</p>
<pre><code> pulp: pulpcore.tasking.services.worker_watcher:INFO: Cleaning up shutdown worker '391@bf917f148de1'.
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: relation "core_worker" does not exist
LINE 1: ...cefully_stopped", "core_worker"."cleaned_up" FROM "core_work...
</code></pre>
<p>Would be nice if it said "migration 00XX_foo conflicts with 00XX_bar" instead.</p> Pulp - Task #7476 (CLOSED - DUPLICATE): [Docs] Improve plugin API reference section of the guidehttps://pulp.plan.io/issues/74762020-09-09T02:51:15Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1933":<a href="https://github.com/pulp/pulpcore/issues/1933" class="external">https://github.com/pulp/pulpcore/issues/1933</a></p>
<hr>
<p><a href="https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide" class="external">https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide</a></p>
<p>Feedback from Gerrod:</p>
<blockquote>
<p>Knowing how Pulp works in order to make changes is definitely the most challenging aspect of contributing. I think the writer’s guide does a good job describing all the different aspects of Pulp and plugins. The plugin api reference section is a bit barren though.</p>
</blockquote>
<p>I think what he's referring to is that several sections like the models and viewsets have almost no description, but then other sections such as downloaders have a lot of detail.</p> Debian Support - Story #7315 (CLOSED - DUPLICATE): Adding RBAC (Role Based Access Control) suppor...https://pulp.plan.io/issues/73152020-08-12T11:29:26Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/392":<a href="https://github.com/pulp/pulp_deb/issues/392" class="external">https://github.com/pulp/pulp_deb/issues/392</a></p>
<hr>
<p>pulpcore 3.6 adds experimental RBAC support. This may be declared safe to use with pulpcore 3.7.</p>
<p>Plugins can start taking advantage of this feature at their own choosing.</p>
<p>Plugin writers doc:</p>
<p><a href="https://github.com/pulp/pulpcore/tree/master/docs/plugins/plugin-writer/concepts/rbac" class="external">https://github.com/pulp/pulpcore/tree/master/docs/plugins/plugin-writer/concepts/rbac</a></p> Debian Support - Task #7024 (CLOSED - DUPLICATE): Add the ability to set per release/distribution...https://pulp.plan.io/issues/70242020-06-22T11:00:38Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/387":<a href="https://github.com/pulp/pulp_deb/issues/387" class="external">https://github.com/pulp/pulp_deb/issues/387</a></p>
<hr>
<p>Right now, users can set the description at the repository level.
This description will be used in the Release file for all releases/distributions in the repository.</p>
<p>We could add a description field to the Release content model, that would override the repository description.</p>
<p>This would be a minor feature addition.</p> RPM Support - Test #6425 (CLOSED - DUPLICATE): Support compressed and uncompressed version of mod...https://pulp.plan.io/issues/64252020-03-31T19:50:25Zfao89
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2240":<a href="https://github.com/pulp/pulp_rpm/issues/2240" class="external">https://github.com/pulp/pulp_rpm/issues/2240</a></p> RPM Support - Test #6349 (CLOSED - DUPLICATE): Test that upload of RPM with large filelists does ...https://pulp.plan.io/issues/63492020-03-16T19:33:49Zfao89
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2236":<a href="https://github.com/pulp/pulp_rpm/issues/2236" class="external">https://github.com/pulp/pulp_rpm/issues/2236</a></p>
<hr>
<ol>
<li>Create an RPM repo.</li>
<li>Verify whether the file <code>RPM_LARGE_METADATA</code> can be uploaded into the repo without errors.</li>
</ol>
<p>RPM_LARGE_METADATA = <a href="https://repos.fedorapeople.org/pulp/pulp/rpm_large_metadata/nodejs-babel-preset-es2015-6.6.0-2.el6.noarch.rpm" class="external">https://repos.fedorapeople.org/pulp/pulp/rpm_large_metadata/nodejs-babel-preset-es2015-6.6.0-2.el6.noarch.rpm</a></p> Pulp - Task #6307 (CLOSED - WONTFIX): Add a CentOS 8 upgrade test to the ansible-pulp-cihttps://pulp.plan.io/issues/63072020-03-06T21:27:19Zmdepaulo@redhat.com
<p>This was not done initially during the ansible-pulp CentOS 8 CI implementation due to lack of time.</p>
<p>Even if the version of pulpcore to install is 3.2.0 (or perhaps earlier via <code>pulpcore_version</code>), we should stilll create a pulp-ci image with molecule, and run the "*upgrade" molecule scenarios against it.</p>