Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-02-19T01:12:08ZPulp
Planio 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 - Story #66 (CLOSED - WONTFIX): As a developer, I have a script to automatically tag a build...https://pulp.plan.io/issues/662014-12-18T16:12:42ZAnonymous
<p>The goal is to provide a script that can be run either by a developer via a jenkins job that can automatically tag a build and release. The script should be able to determine next version number to use. In addition if a flag is specified it should be able to transition the build number from alpha ->beta->rc->release in accordance with <a href="http://pulp-dev-guide.readthedocs.org/en/latest/policies/versioning.html" class="external">http://pulp-dev-guide.readthedocs.org/en/latest/policies/versioning.html</a> In addition the functionality will be provided to automatically merge the changes forward into the next release if there is one. In this way tags from 2.3 will be merged into 2.4, master, etc.</p> Pulp - 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 #64 (CLOSED - WONTFIX): Add man pages for pulp-admin and pulp-clienthttps://pulp.plan.io/issues/642014-12-18T16:12:41ZAnonymousPulp - Story #35 (CLOSED - WONTFIX): As a developer, I have REST API docs for getting plugin infohttps://pulp.plan.io/issues/352014-12-18T16:12:38ZAnonymous
<p>Deliverables: API docs for GET /pulp/api/v2/plugins/types/ API docs for GET /pulp/api/v2/plugins/importers/ API docs for GET /pulp/api/v2/plugins/distributors/ API docs for any other methods that live under /pulp/api/v2/plugins/</p> Pulp - Story #31 (CLOSED - WONTFIX): As a CLI user removing orphans, the pulp-admin tool shows ta...https://pulp.plan.io/issues/312014-12-18T16:12:37ZAnonymous
<p>Deliverables: The orphan remove command in pulp-admin polls task state and displays some type of useful progress info.</p> Puppet Support - Story #32 (CLOSED - WONTFIX): As a developer of pulp_puppet, I have docs about p...https://pulp.plan.io/issues/322014-12-18T16:12:37ZAnonymous
<p>Deliverables: documentation about the format of any progress reports produced by the pulp_puppet plugins.</p> Nectar - Story #29 (CLOSED - WONTFIX): As a developer using nectar, I have documentation of the A...https://pulp.plan.io/issues/292014-12-18T16:12:37ZAnonymous
<p>Deliverables: nectar API documentation any additional documentation of what contract a developer must honor</p> Pulp - Story #30 (CLOSED - WONTFIX): As a developer, I don't hate the configuration value of: che...https://pulp.plan.io/issues/302014-12-18T16:12:37ZAnonymousPulp - Story #26 (CLOSED - WONTFIX): As a Developer, I want a metadata generation libraryhttps://pulp.plan.io/issues/262014-12-18T16:12:36ZAnonymous
<p>Deliverables: Custom library to generate yum metadata information that is geared towards performance for large sets of packages.</p> Pulp - Story #18 (CLOSED - WONTFIX): As a developer, I have an example repository with a distributorhttps://pulp.plan.io/issues/182014-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 - 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 - Story #17 (CLOSED - WONTFIX): As a developer, I have an example repository with extensionshttps://pulp.plan.io/issues/172014-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> RPM Support - Refactor #5 (CLOSED - WONTFIX): [Task] Make pulp_rpm sync use step processing frame...https://pulp.plan.io/issues/52014-12-18T16:12:34ZAnonymousPulp - 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>