Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-08-19T14:09:05ZPulp
Planio RPM Support - Task #9259 (CLOSED - DUPLICATE): workflow-docs should use pulp-cli instead of httpiehttps://pulp.plan.io/issues/92592021-08-19T14:09:05Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2314":<a href="https://github.com/pulp/pulp_rpm/issues/2314" class="external">https://github.com/pulp/pulp_rpm/issues/2314</a></p>
<hr>
<p>Probably shouldn't do this unless/until <strong>all</strong> workflows are supported by pulp-cli commands - mixing pulp-cli and httpie is Very Confusing to the user.</p>
<p>Putting this up as a placeholder for docs-day</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> 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> Pulp - Task #7475 (CLOSED - CURRENTRELEASE): [Docs] Improve testing section of the pulp developer...https://pulp.plan.io/issues/74752020-09-09T02:47:21Zdalleydalley@redhat.com
<p><a href="https://docs.pulpproject.org/pulpcore/en/master/nightly/contributing/tests.html" class="external">https://docs.pulpproject.org/pulpcore/en/master/nightly/contributing/tests.html</a></p>
<p>Feedback from Gerrod:</p>
<blockquote>
<p>For testing it would be helpful to mention the fixtures and building local fixtures with pfixtures if a plugin uses them. It would be helpful to explicitly mention that you should use prestart before testing any changes. Also, running Pulp in the foreground is mentioned, but I think you should also mention pstop and individually stopping and starting the different parts of Pulp like the content server, since these parts are useful to test/debug on their own.</p>
</blockquote> 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> Pulp - Task #6588 (CLOSED - WONTFIX): Verify our systemd unit files in pulp_installer CIhttps://pulp.plan.io/issues/65882020-04-28T14:02:35Zmdepaulo@redhat.com
<p>We should run:</p>
<p><code>systemd-analyze verify /path/to/each/unit_file.service</code></p>
<p><a href="https://github.com/systemd/systemd/issues/3677#issuecomment-552143097" class="external">https://github.com/systemd/systemd/issues/3677#issuecomment-552143097</a></p>
<p>However, it will complain about other unit files. Perhaps the dependencies? So we'd have to parse the output.</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> Pulp - Task #6306 (ASSIGNED): Request EPEL8 versions of packages in the pulp-devel rolehttps://pulp.plan.io/issues/63062020-03-06T21:22:23Zmdepaulo@redhat.com
<p>This PR has to do some workarounds for EL8 support, because the packages were not in EPEL8 yet:
<a href="https://github.com/pulp/ansible-pulp/pull/243/files#" class="external">https://github.com/pulp/ansible-pulp/pull/243/files#</a></p>
<p>Ignoring some helpful developing tools packages:
jnettop
fd-find
fzf</p>
<p>and Installing F28 (Python 3.6) versions of a package we needt:
python3-virtualenvwrapper</p>
<p>and its deps:
python3-virtualenv-clone
python3-stevedore</p>
<p>We should request that they be packaged for EPEL8.
See "## Consumer request for packages"
<a href="https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KXMMLYSAXAVHDKFFBVEFYYZHPJBWXOQQ/" class="external">https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/KXMMLYSAXAVHDKFFBVEFYYZHPJBWXOQQ/</a></p>
<p>And then added to the list of packages to install as normal.</p> Pulp - Task #5107 (CLOSED - DUPLICATE): Add a Makefile template to make it easier to run common p...https://pulp.plan.io/issues/51072019-07-10T13:37:09Zdaviddavis
<p>Inspired by QE's Makefile:</p>
<p><a href="https://github.com/PulpQE/pulp-smash/blob/master/Makefile" class="external">https://github.com/PulpQE/pulp-smash/blob/master/Makefile</a></p>
<p>It would be nice to have something similar for plugins to provide an easy and standardized way to create commands.</p> Debian Support - Task #4150 (CLOSED - WONTFIX): The pool folder structure could be improvedhttps://pulp.plan.io/issues/41502018-11-13T12:22:48Zquba42
<p>When publishing Debian repositories we currently use the following 'pool' folder structure:</p>
<pre><code class="text syntaxhl" data-language="text"><repo_base>/pool/<component>/<files>
</code></pre>
<p>For components like 'main' in Debian this leads to a huge number of files in a single folder.</p>
<p>For this reason the upstream Debian repositories use (one of) the following 'pool' folder structures:</p>
<pre><code class="text syntaxhl" data-language="text"><repo_base>/pool/<component>/<first_char_of_binary_package_name>/<binary_package_name>/<files>
<repo_base>/pool/<component>/lib<fourth_char_of_binary_package_name>/lib<rest_of_binary_package_name>/<files>
</code></pre>
<p>Once the refactoring from <a href="https://github.com/pulp/pulp_deb/pull/57" class="external">https://github.com/pulp/pulp_deb/pull/57</a> is merged, it would be relatively trivial to implement the same pool folder structure Debian uses in pulp_deb.</p>