Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-06-29T19:37:18ZPulp
Planio Pulp - Issue #8988 (CLOSED - CURRENTRELEASE): `pulpcore-worker` startup should remove old worker ...https://pulp.plan.io/issues/89882021-06-29T19:37:18Zbmbouterbmbouter@redhat.com
<a name="To-reproduce"></a>
<h2 >To reproduce<a href="#To-reproduce" class="wiki-anchor">¶</a></h2>
<ol>
<li>Start a pulpcore-worker against an empty database</li>
<li>Observe that the status API shows that worker</li>
<li>kill -9 your worker</li>
<li>Observe the status API after 30 seconds no longer shows your worker</li>
<li>Start your pulpcore-worker again</li>
<li>Go into shell_plus and observe this query shows 2 workers present: <code>Workers.objects.count()</code>
</li>
</ol>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<pre><code>In [1]: Worker.objects.count()
Out[1]: 1
</code></pre>
<a name="Solution"></a>
<h2 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>Have workers that startup run a query that delete any workers that haven't issued a heartbeat in say 7 days. This does not need to be configurable. The 7 day idea is to make something that won't let records accumulate on the long term, but leave them in place for someone to look at the db post-mortem and still see them for investigation.</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> 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 - Issue #7715 (CLOSED - CURRENTRELEASE): Spelling error in import-export workflow dochttps://pulp.plan.io/issues/77152020-10-15T15:35:04Zggainey
<p>From <a href="https://docs.pulpproject.org/pulpcore/workflows/import-export.html" class="external">https://docs.pulpproject.org/pulpcore/workflows/import-export.html</a>:</p>
<p>"Finally, if we need complete comtrol over incremental exporting, " - 'comtrol' is not a word :)</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 - Issue #6564 (CLOSED - CURRENTRELEASE): Export filename for pulp exports has dupe slasheshttps://pulp.plan.io/issues/65642020-04-23T17:47:05ZdaviddavisCertGuard - Issue #6424 (CLOSED - CURRENTRELEASE): An expired client RHSM Certificate should be d...https://pulp.plan.io/issues/64242020-03-31T19:43:21Zbmbouterbmbouter@redhat.comPulp - 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 - Issue #6243 (CLOSED - CURRENTRELEASE): When pip_version_specifier is set to null, broken c...https://pulp.plan.io/issues/62432020-02-28T18:40:00Zttereshcttereshc@redhat.com
<p>One can specify a pip_version_specifier to point to a specific plugin release.
There is also a pulpcore_pip_version_specifier which points to a specific pulpcore release.</p>
<p>On the master branch it makes sense to unset those and have them set only for releases.</p>
<p>Their behaviour is inconsistent when they are unset and might lead to a broken config.
To use the latest PyPI release, one can set pulpcore_pip_version_specifier to 'null'.
To use the latest PyPI release for plugins, one must remove it from the config, because setting it to 'null' will generate a broken config, it adds 'None' to the plugin name.</p>
<pre><code class="diff syntaxhl" data-language="diff"> - pulp-2to3-migration-${TAG}:
image_name: pulp-2to3-migration
tag: $TAG
<span class="gd">- pulpcore: pulpcore~=3.0.0
</span><span class="gi">+ pulpcore: pulpcore
</span> plugins:
- ./pulp-2to3-migration
<span class="gd">- - pulp_file~=0.1.0
- - pulp_container~=1.0.0
</span><span class="gi">+ - pulp_fileNone
+ - pulp_containerNone
+ - pulp_rpmNone
</span></code></pre> Migration Plugin - Issue #6111 (CLOSED - CURRENTRELEASE): Re-migrations take nearly as long as in...https://pulp.plan.io/issues/61112020-02-07T14:31:24Zdalleydalley@redhat.com
<p>With a large repository, re-migrations take a very long time.</p>
<pre><code><jsherrill> i was also planning on testing re-migration time with that repo
<jsherrill> and that seemed really really slow
<jsherrill> but i wasn't sure if that was related to the fact that not all of the units migrated properly
<jsherrill> so was waiting for it to be fixed to test for sure
<jsherrill> like it seemed like it took ~an hour to re-migrate it
<jsherrill> i'm sure there is a lot of low-hanging fruit performance wise
<jsherrill> and i'm less concerned about initial migration time
</code></pre> 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 - Issue #5162 (CLOSED - CURRENTRELEASE): Ruby bindings, WARNING: license value 'GPLv2' is in...https://pulp.plan.io/issues/51622019-07-21T10:32:16Zttereshcttereshc@redhat.com
<p>It doesn't prevent bindings from publishing.<br>
I'm not sure how important it is for Ruby clients/community. E.g. in case they have a check or a filter by license or something similar.</p>
<pre><code>WARNING: license value 'GPLv2' is invalid. Use a license identifier from
http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
Did you mean 'GPL-2.0', 'LGPLLR', 'NGPL'?
WARNING: See http://guides.rubygems.org/specification-reference/ for help
</code></pre>
<p>Travis job: <a href="https://travis-ci.org/pulp/pulp_rpm/jobs/561431496" class="external">https://travis-ci.org/pulp/pulp_rpm/jobs/561431496</a></p> 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>