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 - 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> 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 #1804 (CLOSED - WONTFIX): Create monthly view for community statisticshttps://pulp.plan.io/issues/18042016-03-31T14:55:28ZAnonymous
<p>Collect data from IRC, website, and github. Compose into an ongoing monthly report.</p> RPM Support - Story #211 (CLOSED - WONTFIX): [RFE] pulp allows corrupt rpms to be pushed into reposhttps://pulp.plan.io/issues/2112015-02-19T01:12:08ZAnonymous
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1023335" class="external">Bugzilla Bug #1023335</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
I create a repo, and push to it a corrupt rpm, which won't install.</p>
<p>Version-Release number of selected component (if applicable):<br>
2.2.0-1</p>
<p>How reproducible:<br>
always</p>
<p>Steps to Reproduce:</p>
<p>1. locate a corrupt rpm:<br>
rpm -K /tmp/corruptrpm-1.0-1.noarch.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#f44e7eb7)</p>
<p>2. pulp-admin rpm repo create --repo-id test-repo2 --relative-url test-repo2</p>
<p>3. pulp-admin rpm repo uploads rpm -f /tmp/corruptrpm-1.0-1.noarch.rpm --repo-id=test-repo2<br>
<span>----------------------------------------------------------------------</span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
[==================================================] 100%<br>
Analyzing: corruptrpm-1.0-1.noarch.rpm<br>
... completed</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing: corruptrpm-1.0-1.noarch.rpm<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
cancelled entirely using the cancel command.</p>
<p>Uploading: corruptrpm-1.0-1.noarch.rpm<br>
[==================================================] 100%<br>
2729160/2729160 bytes<br>
... completed</p>
<p>Importing into the repository...<br>
... completed</p>
<p>Deleting the upload request...<br>
... completed</p>
<p>Actual results:</p>
<p>Corrult rpm successfully pushed into pulp.</p>
<p>Expected results:</p>
<p>rpm upload should fail due to incorrect checksum</p>
<p>Additional info:</p>
<p>--- Additional comment from <a href="mailto:petter.hassberg@netent.com" class="email">petter.hassberg@netent.com</a> at 10/25/2013 08:49:45 ---</p>
<p>this was not a corrupt rpm after all.</p>
<p>--- Additional comment from <a href="mailto:petter.hassberg@netent.com" class="email">petter.hassberg@netent.com</a> at 11/11/2013 14:49:22 ---</p>
<p>This also is applicable with actual corrupt rpm:s with sha1sum mismatch,.</p>
<p>--- Additional comment from <a href="mailto:skarmark@redhat.com" class="email">skarmark@redhat.com</a> at 11/13/2013 16:56:04 ---</p>
<p>***** Bug 1029085 has been marked as a duplicate of this bug. ***</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 #76 (CLOSED - WONTFIX): Automatically run repoclosure for all arches/dists after buil...https://pulp.plan.io/issues/762014-12-18T16:12:43ZAnonymous
<p>This task is related to build stuff, not Pulp itself:)</p>
<p>RPM dependences are occasionally missed during a build, especially for platforms we do not commonly use like el5. This occurs about once every two or three weeks for Pulp repos; QE will find that an RPM is missing while doing an install.</p>
<p>One way to find such issues quickly is to run repoclosure on each repos before publishing. This is typically done as one command per repo; an example is at <a href="https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Repoclosure" class="external">https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Repoclosure</a>.</p>
<p>This step is typically done during the build/release process before QE handoff, but could also be done by QE. Ideally this could be run as part of the new build process.</p>
<p>This should be done in the nightly Jenkins build repos job. This should be done using Docker if possible because it needs to be run on each arch and dist.</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 - Story #69 (CLOSED - WONTFIX): As a user, I'd like to be able to upgrade pulp packages on c...https://pulp.plan.io/issues/692014-12-18T16:12:42ZAnonymous
<p>Users would like to upgrade pulp packages on consumers using Pulp. This will require API compatibility and the ability for the Pulp server to initiate restarted the agent.The flow:1. Upgrade the pulp server.2. Send content update request to one or more consumers. Something like 'pulp-admin rpm consumer update run --consumer-id=ABC -n \*pulp\*'And have it work.</p> Pulp - Story #68 (CLOSED - WONTFIX): As a user, I can find out if a child node is out of sync wit...https://pulp.plan.io/issues/682014-12-18T16:12:42ZAnonymous
<p>Katello needs a way to know if a repo on a pulp node is out of sync with its upstream repo. Potentially knowing what is out of sync would be nice, but just knowing that it is out of sync is needed.</p>