Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-08-19T13:09:02ZPulp
Planio Pulp - Issue #7347 (CLOSED - CURRENTRELEASE): OpenAPI specs: reserved_resources_record missing fr...https://pulp.plan.io/issues/73472020-08-19T13:09:02ZAnonymous
<p>In <code>pulpcore-3.6.0</code>, OpenAPI specs no longer advertise <code>reserved_resources_record</code> field in <code>TaskResponse</code>, and subsequently the field is no longer available in <code>pulpcore-client</code> bindings (for 3.6.0). The actual REST API response <strong>does</strong> contain that field.</p>
<p>Please ensure the field is available in the client bindings again, as it is vital to some Pulp applications (RHUI).</p> Pulp - Issue #2079 (CLOSED - DUPLICATE): Fails to sync EPEL 7.x repository with Pulp 2.9.0https://pulp.plan.io/issues/20792016-07-14T14:01:27ZAnonymous
<p>I was trying to synchronize my EPEL 6.x/7.x repositories using the workaround published here.</p>
<p><a href="http://www.pulpproject.org/2016/07/12/pulp-2-9-0-generally-available/" class="external">http://www.pulpproject.org/2016/07/12/pulp-2-9-0-generally-available/</a></p>
<p>The migration took a little while but after applying the work around i get the following error ONLY on EPEL 7.x repository.</p>
<pre><code>pulp-admin rpm repo sync run --repo-id epel-7-x86_64
+----------------------------------------------------------------------+
Synchronizing Repository [epel-7-x86_64]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Downloading metadata...
[/]
... completed
Downloading repository content...
[|]
[============= ] 27%
RPMs: 2/3 items
Delta RPMs: 0/0 items
... completed
Downloading distribution files...
[==================================================] 100%
Distributions: 0/0 items
... completed
Importing package groups/categories...
[\]
... completed
Cleaning duplicate packages...
[\]
... completed
Task Succeeded
Initializing repo metadata
[-]
... completed
Publishing Distribution files
[-]
... completed
Publishing RPMs
[==================================== ] 72%
7495 of 10349 items
Task Failed
Invalid block tag: 'compress'
</code></pre>
<p>This does not happen on EPEL 6.x repository and I try the following in order to fix the problem with no luck.</p>
<p>1. Delete the EPEL 7.x repository<br>
2. Create a new EPEL repository<br>
3. Update the repo using the workaround --skip...<br>
4. Synchronize again</p> Pulp - Issue #694 (CLOSED - NOTABUG): pulp-admin should support SNIhttps://pulp.plan.io/issues/6942015-02-28T23:23:28ZAnonymous
<p>Description of problem:</p>
<p>If several SSL vhosts are sharing the same HTTPS port but have different TLS certificates, pulp-admin fails to verify the server's certificate.</p>
<p>Therefor SNI support for the admin client pulp-admin is required.</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1. Setup vhosts using the same HTTPS port with different certificates<br>
2. login to pulp<br>
3. enter "pulp-admin repo list"</p>
<p>Actual results:</p>
<p>pulp-admin throws an error, telling the common name does not match peer's name.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1191921" class="external">Bugzilla Bug #1191921</a> +</p> Nectar - Story #11 (CLOSED - WONTFIX): Nectar: Add concept of download retries and timeouthttps://pulp.plan.io/issues/112014-12-18T16:12:35ZAnonymousRPM Support - Story #12 (CLOSED - DUPLICATE): As a user, I can upload environment groupshttps://pulp.plan.io/issues/122014-12-18T16:12:35ZAnonymous
<p>Deliverables:</p>
<ul>
<li>yum importer can handle uploads of environment groups</li>
<li>CLI has a command to upload environment groups</li>
</ul> Docker Support - Story #13 (CLOSED - WONTFIX): As a user I can install the pulp-docker-registry a...https://pulp.plan.io/issues/132014-12-18T16:12:35ZAnonymous
<p>As a user I can install the pulp-docker-registry app onto OpenShiftPerform whatever additional packaging must be done after this app is packaged as an RPM in order to make it available via OpenShift</p> Pulp - Story #14 (CLOSED - NOTABUG): As a user I can rely on node having 100% unit test coverage ...https://pulp.plan.io/issues/142014-12-18T16:12:35ZAnonymous
<p>We need to write unit tests for coverage that was provided by integration tests that were removed during migration to celery.We will separately advise the QE team on how to create test cases in their automated suite.</p> Pulp - Story #15 (CLOSED - WONTFIX): As a user, I can rest easy in the knowledge that my celery w...https://pulp.plan.io/issues/152014-12-18T16:12:35ZAnonymous
<p>We should configure Pulp to use Celery's message signing feature[0]. This will add a layer of security to protect the Celery workers from performing tasks that might have been injected by an attacker.Deliverables:Pulp server can be configured to sign messagesPulp workers can be configured to require valid signatures on messagesDocument how users can configure message signing[0] <a href="http://celery.readthedocs.org/en/latest/userguide/security.html#message-signing" class="external">http://celery.readthedocs.org/en/latest/userguide/security.html#message-signing</a></p> Pulp - Story #16 (CLOSED - WONTFIX): As a developer, I have an example repository with an importerhttps://pulp.plan.io/issues/162014-12-18T16:12:35ZAnonymous
<p>As discussed during the Pulp Summit, we should have a git repository that contains an example of simple type support.Deliverablesnew git repository with support for a basic content type, such as perhaps generic filesimporter, distributor, and admin extensionsextensive in-line code documentationdeveloper guide that includes all pertinent informationwhenever possible, ensure that generic functionality is in the platform</p> Pulp - Refactor #9 (CLOSED - DUPLICATE): As a developer, I would like /etc/pulp/repo_auth.conf to...https://pulp.plan.io/issues/92014-12-18T16:12:34ZAnonymous
<p>Some of the repo auth code in pulp_rpm but should be in platform so other plugins can use it without depending on pulp_rpm being installed.This was originally related to <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1140823" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1140823</a></p> Puppet Support - Task #3 (CLOSED - NOTABUG): Make pulp_puppet publish use step processing frameworkhttps://pulp.plan.io/issues/32014-12-18T16:12:34ZAnonymousPuppet Support - Task #4 (CLOSED - NOTABUG): Make pulp_puppet sync use step processing frameworkhttps://pulp.plan.io/issues/42014-12-18T16:12:34ZAnonymousRPM Support - Refactor #5 (CLOSED - WONTFIX): [Task] Make pulp_rpm sync use step processing frame...https://pulp.plan.io/issues/52014-12-18T16:12:34ZAnonymousDocker Support - Story #6 (CLOSED - WONTFIX): As pulp_docker, I recognize when an upload's file i...https://pulp.plan.io/issues/62014-12-18T16:12:34ZAnonymous
<p>Deliverables:When initiating an upload, and the file being uploaded has been uploaded before, pulp recognizes this and does not re-upload the file.</p> Docker Support - Story #8 (CLOSED - WONTFIX): As a user, I can serve docker images with entitleme...https://pulp.plan.io/issues/82014-12-18T16:12:34ZAnonymous
<p>On 10/6/14, bkearney stated during a phone meeting that for satellite 6.1, doing entitlement enforcement via crane only is sufficient. We do not need to do enforcement when serving the image files via pulp.</p>