Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-10-28T13:33:40ZPulp
Planio Pulp - Story #7762 (CLOSED - WONTFIX): Need synchronous REST endpoint for (RPM) distribution updatehttps://pulp.plan.io/issues/77622020-10-28T13:33:40ZAnonymous
<p>In a typical RHUI setup with 400+ repos and similar number of pending repository sync tasks,
it would be of a great help to have ability to "publish" (ie. update their distribution with a publication
that is already available) those repos that already have the latest
metadata compiled without waiting for the sync task queue to drain. Alternatively, a way to "push"
newly created distribution update onto the start of the task queue. In my understanding, updating a
distribution looks like a lightweight task compared to sync or metadata generation tasks.</p> 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 - Story #5662 (CLOSED - CURRENTRELEASE): Manage Pulp via Ansible moduleshttps://pulp.plan.io/issues/56622019-11-04T16:15:21ZAnonymous
<p>I've been testing ansible modules to manage Pulp.</p>
<p><a href="https://github.com/ansible/ansible/pull/64388" class="external">https://github.com/ansible/ansible/pull/64388</a></p>
<p>Please let me know what you think.</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> Nectar - Story #1915 (CLOSED - WONTFIX): expose connect_timeout and read_timeout via configurationhttps://pulp.plan.io/issues/19152016-05-12T15:48:00ZAnonymous
<p>My pulp installation was having issues completing synchronization of certain external repos due to timeouts. Following discussions on this thread[0], I found that I was able to resolve this timeout by increasing the values found in /usr/lib/python2.6/site-packages/nectar/config.py:22.</p>
<p>I'm hoping that these timeout values can be made available from a configuration file.</p>
<p>My patch diff (rpm python-nectar-1.5.1-1.el6.noarch):</p>
<pre><code class="c syntaxhl" data-language="c"><span class="mi">22</span><span class="n">c22</span>
<span class="o"><</span> <span class="n">connect_timeout</span><span class="o">=</span><span class="mi">9</span><span class="p">.</span><span class="mo">05</span><span class="p">,</span> <span class="n">read_timeout</span><span class="o">=</span><span class="mi">57</span><span class="p">,</span> <span class="n">working_dir</span><span class="o">=</span><span class="s">"/tmp"</span><span class="p">)</span><span class="o">:</span>
<span class="o">---</span>
<span class="o">></span> <span class="n">connect_timeout</span><span class="o">=</span><span class="mi">6</span><span class="p">.</span><span class="mo">05</span><span class="p">,</span> <span class="n">read_timeout</span><span class="o">=</span><span class="mi">27</span><span class="p">,</span> <span class="n">working_dir</span><span class="o">=</span><span class="s">"/tmp"</span><span class="p">)</span><span class="o">:</span>
</code></pre>
<p>[0] <a href="https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w" class="external">https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w</a></p> Pulp - Task #1803 (CLOSED - CURRENTRELEASE): Plan replacement of mongodb with postgreshttps://pulp.plan.io/issues/18032016-03-31T14:53:39ZAnonymousPulp - 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> Pulp - Refactor #78 (CLOSED - WONTFIX): Convert pulp.server.db.connection to manage the database ...https://pulp.plan.io/issues/782014-12-18T16:12:43ZAnonymous
<p>This Task is designed to solve two problems. (1) To remove the use of globals and replace it with a class based design and (2) to consolidate the database getter methods onto the class managing the database singleton.</p>
<p>I generally avoid the use of globals because they casually share state and promote a non object oriented paradigm. Using a class to store any globals requires developers to be more explicit, and access functions can be getter methods instead of module level functions.</p>
<p>The specifics:<br>
1) Introduce a new class in pulp.server.db.connection and move the initialize method into it as a @classmethod. Refactor all calls to the old pulp.server.db.connection.initialize method to use the new class method. The @classmethod initialize should store the _CONNECTION and _DATABASE objects as class attributes.</p>
<p>2) Move the get_collection(), get_database(), and get_connection() methods to be @classmethods on the new class introduced in (1). Refactor the usages of these 3 functions to use them as classmethods.</p>
<p>3) Ensure that get_collection(), get_database(), and get_connection() raise a consistent Exception if initialize() has not already been called.</p>
<p>4) Update the associated tests</p> Pulp - Refactor #77 (CLOSED - WONTFIX): Reduce bind complexityhttps://pulp.plan.io/issues/772014-12-18T16:12:43ZAnonymous
<p>In early 2.x our bind model and flows was augmented to include tracking consumer (agent) confirmation. The proposal here is to do away with this tracking in both the bind model and the bind/unbind flows. If we still think this information is useful, we can discuss having the agent periodically report the bindings and store them separately like package profile.</p> Pulp - Task #75 (CLOSED - WONTFIX): As a user, I can trust that Pulp's versions are correct with ...https://pulp.plan.io/issues/752014-12-18T16:12:43ZAnonymous
<p>Err:509</p> Pulp - Task #74 (CLOSED - WONTFIX): As a user, I can install the pulp-agent without pulp-clienthttps://pulp.plan.io/issues/742014-12-18T16:12:43ZAnonymous
<p>The consumer packages should be decoupled from pulp-agent. The packaging should be adjusted so that the common components are located in a package such as pulp-consumer-common, and both pulp-agent and pulp-consumer-client should use pulp-consumer-common.The docs also need to be updated.</p> Puppet Support - Task #73 (CLOSED - WONTFIX): Pulp puppet tests should mirror python path hierarchyhttps://pulp.plan.io/issues/732014-12-18T16:12:42ZAnonymous
<p>It seems all of the pulp puppet unit tests are contained at pulp_puppet_plugins/test/unit/These tests do not follow the convention of mirroring the python path hierarchy with directories in the test folder.The existing tests should be re-worked to mirror the python path hierarchy as they do in pulp platform.</p> Pulp - Task #72 (CLOSED - WONTFIX): Separate unit tests and integration tests by plugin (and plat...https://pulp.plan.io/issues/722014-12-18T16:12:42ZAnonymousPulp - Story #71 (CLOSED - WONTFIX): As a developer, I would like an automated job to test pulp u...https://pulp.plan.io/issues/712014-12-18T16:12:42ZAnonymous
<p>Currently there is no developer automation around upgrade testing. The following scenarios would be nice:2.3 latest-> 2.4 latest2.4 latest released beta to 2.4 latest (not officially supported but would be good to know when it breaks)</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>