Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-02-08T18:18:29ZPulp
Planio 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> 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 #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> 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> RPM Support - Story #5740 (CLOSED - CURRENTRELEASE): As a user, advisory collection names are uni...https://pulp.plan.io/issues/57402019-11-18T11:56:24Zttereshcttereshc@redhat.com
<a name="Background"></a>
<h3 >Background<a href="#Background" class="wiki-anchor">¶</a></h3>
<p>As a part of <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: As a user, a repository version has no advisories with the same id (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/4295">#4295</a>, two advisories can be merged into a new one which contains combined package list.</p>
<a name="Motivation"></a>
<h3 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h3>
<p>Each package list consists of collections (usually 1 , but can be 0 or 2+ as well). Each collection has a name which is expected to be unique by dnf/yum client. If the name is not unique, only a subset of packages will be updated when advisory is applied on a user system.</p>
<a name="Solution"></a>
<h3 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h3>
<p>Ensure the uniqueness of collection names at the time of combining two advisories into one.<br>
If names are unique, preserve original names.<br>
If names are the same, make them unique (e.g. append an ordinal number to the existing name)</p> Pulp - Story #5559 (CLOSED - CURRENTRELEASE): As a plugin writer, I cannot export my Publication ...https://pulp.plan.io/issues/55592019-10-08T16:50:04Zbmbouterbmbouter@redhat.com
<p>Say you create a Publication with 3 PublishedMetadata objects, each with an Artifact to be served to the user for that relative_path. Note <code>/foo</code> also has an Artifact.</p>
<ul>
<li>relative_path: <code>/foo</code>
</li>
<li>relative_path: <code>/foo/bar</code>
</li>
<li>relative_path: <code>/foo/baz</code>
</li>
</ul>
<p>You can't create this on a POSIX filesystem because of the file/directory conflict on <code>foo</code>.</p>
<pre><code>[bmbouter@localhost tmp]$ touch foo
[bmbouter@localhost tmp]$ mkdir foo
mkdir: cannot create directory ‘foo’: File exists
</code></pre>
<p>This prevents users from exporting the Artifacts from a Publication to POSIX filesystems.</p> RPM Support - Story #5356 (CLOSED - CURRENTRELEASE): As a user, I can download a configuration fo...https://pulp.plan.io/issues/53562019-08-27T12:28:24Zdkliban@redhat.com
<p>It is common for repositories to include a repo file that can be used to add the repository to a client. This file can be manually placed into /etc/yum.repos.d/ or it can be specified as a parameter to yum/dnf. e.g.</p>
<pre><code>dnf config-manager --add-repo http://example.com/pulp/content/some/repo/path/config.repo
</code></pre> Pulp - Test #4362 (CLOSED - COMPLETE): Ansible installer for Pulp3 needs to add a systemd unit fi...https://pulp.plan.io/issues/43622019-01-30T14:41:28Zbherring
<a name="Testing"></a>
<h2 >Testing<a href="#Testing" class="wiki-anchor">¶</a></h2>
<ul>
<li>Need to investigate if there is an issue here or not (from Triage)</li>
</ul> Container Support - Story #4171 (CLOSED - CURRENTRELEASE): As a user i can configure download of ...https://pulp.plan.io/issues/41712018-11-19T10:23:15Zipanova@redhat.comipanova@redhat.com
<p>Some images like windows base images, contain artifacts whose distribution is restricted by license.<br>
When these images are pushed to a registry, restricted artifacts are skipped/not included by default.</p>
<p>These artifacts are called foreign layers and have "mediaType": "application/vnd.docker.image.rootfs.foreign.diff.tar.gzip"</p>
<p>Remote should have a Boolean "*allow_foreign_layers*" option which would control the download of the foreign layers.</p>
<p><strong>Set to False (default):</strong><br>
Pulp will check the mediatype and simply will skip the foreign layers.<br>
Case: do not sync content which is restricted by a license without explicit acknowledgment in the Remote config<br>
From client side, it will follow the url specified in the details of the layer in the manifest.</p>
<p><strong>Set to True:</strong><br>
Pulp will download the foreign layers by following the url.<br>
Case: due to use case of registries with air gaped network, now it's possible to push to the registry foreign layers, by enabling -allow-nondistributable-artifacts daemon option. From client side, foreign layers are now pulled from the registry if possible, falling back to the URLs in the image manifest otherwise. As far as i know that's done in docker for Windows. Linux version is still ignoring foreign layers during pull.</p> Pulp - Task #3930 (CLOSED - CURRENTRELEASE): Validate commit messageshttps://pulp.plan.io/issues/39302018-08-23T15:27:20Zdaviddavis
<a name="The-Problem"></a>
<h2 >The Problem<a href="#The-Problem" class="wiki-anchor">¶</a></h2>
<p>Two problems we have dealt with recently:</p>
<ul>
<li>A commit was attached to an issue that was already released. Thus the commit was left out of the build it was intended for.</li>
<li>A commit for an issue got merged that was not attached to the issue. This commit was also left out of a build.</li>
</ul>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>The solution we'd like to propose is to validate that each commit message is:</p>
<ul>
<li>attached to an issue</li>
<li>the issue is in the correct state (NEW, ASSIGNED, POST, or MODIFIED)</li>
</ul>
<p>We discussed that this should be non-blocking as sometimes commits for small items (fixing typos) don't need an issue. However, this is tricky as Travis can only pass/fail PRs.</p>
<p>I'd propose that commit messages that aren't attached to issues have the tag "#noissue" in them. This would exclude them from this validation.</p> Pulp - Task #3144 (CLOSED - CURRENTRELEASE): As an authenticated user, I can filter tasks.https://pulp.plan.io/issues/31442017-11-17T18:51:33Zdaviddavis
<p>User story examples:</p>
<ul>
<li>As a user, I want to filter by tasks by state in order to see if tasks are failing/running/etc.</li>
<li>As a user, I want to see all tasks that ran in a given time in order to see what affected system performance or in order to debug an error.</li>
<li>As a user, I can filter sync tasks by a repository.</li>
<li>As a user, I want to get all the tasks of a specific type (e.g. sync) to know if there are any outliers in terms of performance.</li>
</ul>
<p>Fields:</p>
<ul>
<li>state (equality, state_in_list)</li>
<li>started_at(started_in_range)</li>
<li>finished_at(finished_in_range)</li>
<li>worker (equality)</li>
</ul> Pulp - Refactor #2963 (CLOSED - CURRENTRELEASE): Use the new lower case celery config settingshttps://pulp.plan.io/issues/29632017-08-08T14:28:15Zdaviddavis
<p>Celery 4 introduces new config settings with better naming. More info:</p>
<p><a href="http://docs.celeryproject.org/en/latest/userguide/configuration.html#new-lowercase-settings" class="external">http://docs.celeryproject.org/en/latest/userguide/configuration.html#new-lowercase-settings</a></p> Pulp - Task #2817 (CLOSED - CURRENTRELEASE): Remove Scratchpad from Pulp 3https://pulp.plan.io/issues/28172017-06-13T16:15:27Zamacdona@redhat.comaustin@redhat.com
<p>Remove the Scratchpad model and all uses of it.</p>
<p>The model is here[0].</p>
<p>[0]: <a href="https://github.com/pulp/pulp/blob/253ae59c9d80a4698c47a0608f96e5d81a62f0d7/platform/pulpcore/app/models/generic.py#L158-L160" class="external">https://github.com/pulp/pulp/blob/253ae59c9d80a4698c47a0608f96e5d81a62f0d7/platform/pulpcore/app/models/generic.py#L158-L160</a></p> Pulp - Story #2421 (CLOSED - CURRENTRELEASE): As a user I can manage Pulp's database migrations u...https://pulp.plan.io/issues/24212016-11-14T16:05:00Zdkliban@redhat.com
<p>In Pulp 2.Y, users use pulp-manage-db to migrate their database when installing for the first time or upgrading to a new version.</p>
<p>It's important that users are able to continue to run migrations in Pulp 3.Y. Since we are leveraging Django's migration management capabilities, Pulp users will need to use the manage.py that is part of the Pulp Django app.</p>
<p>As a result of this story, a new executable should be created. This executable will take the same arguments that manage.py takes and simply forward them to the manage.py in the Pulp app that is installed.</p>
<p>We can add any custom commands we need[0]. One such command could be 'reset-admin-pass' as I mentioned here[1].</p>
<p>A possible name for the executable is 'pulp-manager'.</p>
<p>[0] <a href="https://docs.djangoproject.com/en/1.8/howto/custom-management-commands/" class="external">https://docs.djangoproject.com/en/1.8/howto/custom-management-commands/</a><br>
[1] <a href="https://pulp.plan.io/issues/2358?pn=1#note-8" class="external">https://pulp.plan.io/issues/2358?pn=1#note-8</a></p> Pulp - Story #176 (CLOSED - CURRENTRELEASE): [RFE] Refactor config.get_boolean to raise ValueErro...https://pulp.plan.io/issues/1762015-02-19T01:03:52Zrbarlow
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=915462" class="external">Bugzilla Bug #915462</a> +</span>+</p>
<p>Description of problem:</p>
<p>This method currently returns None when it cannot parse a boolean from its input. It would be more appropriate for it to raise ValueError.</p>
<p>--- Additional comment from <a href="mailto:cduryee@redhat.com" class="email">cduryee@redhat.com</a> at 11/18/2014 00:07:33 ---</p>
<p>This is still the behavior as of 2.4.3.</p>