Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-09-09T02:51:15ZPulp
Planio Pulp - Task #7476 (CLOSED - DUPLICATE): [Docs] Improve plugin API reference section of the guidehttps://pulp.plan.io/issues/74762020-09-09T02:51:15Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/1933":<a href="https://github.com/pulp/pulpcore/issues/1933" class="external">https://github.com/pulp/pulpcore/issues/1933</a></p>
<hr>
<p><a href="https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide" class="external">https://docs.pulpproject.org/pulpcore/plugins/index.html#plugin-writer-s-guide</a></p>
<p>Feedback from Gerrod:</p>
<blockquote>
<p>Knowing how Pulp works in order to make changes is definitely the most challenging aspect of contributing. I think the writer’s guide does a good job describing all the different aspects of Pulp and plugins. The plugin api reference section is a bit barren though.</p>
</blockquote>
<p>I think what he's referring to is that several sections like the models and viewsets have almost no description, but then other sections such as downloaders have a lot of detail.</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 - Story #264 (CLOSED - WONTFIX): [RFE] Content searches should provide a direct download lin...https://pulp.plan.io/issues/2642015-02-19T01:20:01Ztvaughan@onyxpoint.comtvaughan@onyxpoint.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1156067" class="external">Bugzilla Bug #1156067</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>When doing a content search, the information returned should include a direct download link if one is available. This would remove the need for another mile of typing to pull the file out of the repo.</p> Pulp - Story #263 (CLOSED - WONTFIX): [RFE] Need the ability to run operations on multiple reposi...https://pulp.plan.io/issues/2632015-02-19T01:19:57Ztvaughan@onyxpoint.comtvaughan@onyxpoint.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1156059" class="external">Bugzilla Bug #1156059</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>When using the Pulp command line utilities, I find it irritating to be limited to one repository at a time.</p>
<p>I would like to be able to either omit the repo-id and search all repositories or specify a regex.</p>
<p>For instance: I want to find the latest version of BASH in <strong>any</strong> centos7 repository.</p>
<p>What I currently have to do:</p>
<p>for x in `pulp-admin rpm repo search --fields name | grep Id | sed 's/<a class="wiki-page new" href="https://pulp.plan.io/projects/pulp/wiki/Space">:space:</a>\+/ /' | cut -f2 -d' '`; do pulp-admin rpm repo content rpm --repo-id=$x --match='name=^bash.*'; done</p>
<p>This is crazy.</p>
<p>What I want to do:</p>
<p>pulp-admin rpm repo content rpm --match='name=^bash.*' --repo-id='^centos7.*'</p>
<p>Additionally, when I want to sync all repos I just want to omit the --repo-id and have it sync ALL repos...now (maybe with a splay).</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>All</p>
<p>How reproducible:</p>
<p>See above</p>
<p>Actual results:</p>
<p>For loops of irritation</p>
<p>Expected results:</p>
<p>Clean and intuitive user experience</p> Pulp - Story #249 (CLOSED - WONTFIX): [RFE] nested pulp-admin sessionshttps://pulp.plan.io/issues/2492015-02-19T01:19:05Zigulina@redhat.comigulina@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1134510" class="external">Bugzilla Bug #1134510</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:</p>
<p>Pulp-admin supports login command from one user to another without prior logout.<br>
So far, every new login command rewrite/removes the granted certificate of the previous user. After logout command the user doesn't have his session back with a granted certificate anymore. So s/he has to login again.</p>
<p>Nested sessions like in bash shell would be nice feature especially for users with admin roles.</p>
<p>Steps to Reproduce:</p>
<blockquote>
<blockquote>
<p>pulp-admin login -u admin -p admin</p>
</blockquote>
</blockquote>
<p>Successfully logged in. Session certificate will expire at Oct 9 20:19:42 2015<br>
GMT.</p>
<blockquote>
<blockquote>
<p>pulp-admin repo list</p>
</blockquote>
</blockquote>
<p><span><del>--------------------------------------------------------------------</del></span><br>
Repositories<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Id: gena<br>
Display Name: gena<br>
Description: None<br>
Content Unit Counts:</p>
<blockquote>
<blockquote>
<p>pulp-admin login -u user1 -p test1</p>
</blockquote>
</blockquote>
<p>Successfully logged in. Session certificate will expire at Oct 9 20:20:23 2015<br>
GMT.</p>
<blockquote>
<blockquote>
<p>pulp-admin repo list</p>
</blockquote>
</blockquote>
<p><span><del>--------------------------------------------------------------------</del></span><br>
Repositories<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Insufficient Permissions</p>
<p>The user does not have the appropriate permissions to execute this command.</p>
<blockquote>
<blockquote>
<p>pulp-admin logout</p>
</blockquote>
</blockquote>
<p>Session certificate successfully removed.</p>
<blockquote>
<blockquote>
<p>pulp-admin repo list</p>
</blockquote>
</blockquote>
<p><span><del>--------------------------------------------------------------------</del></span><br>
Repositories<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Authentication Failed</p>
<p>Use the login command to authenticate with the server and download a session<br>
certificate for use in future calls to this script. If credentials were<br>
specified, please double check the username and password and attempt the request<br>
again.</p>
<p>Expected results:</p>
<p>1. Log as user <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' p... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1">#1</a><br>
2. Execute some pulp-admin commands without -u/-p options<br>
3. Log as user <a class="issue tracker-3 status-11 priority-7 priority-high2 closed" title="Story: As a user, my rpm sync finishes quickly when upstream metadata hasn't changed (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/2">#2</a> without logout from the user <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' p... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1">#1</a> session<br>
4. Execute some pulp-admin commands without -u/-p options as user <a class="issue tracker-3 status-11 priority-7 priority-high2 closed" title="Story: As a user, my rpm sync finishes quickly when upstream metadata hasn't changed (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/2">#2</a><br>
5. logout<br>
6. return back to the session of user <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' p... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1">#1</a> and be able to execute pulp-admin commands without -u/-p options since the certificate of user <a class="issue tracker-3 status-11 priority-6 priority-default closed child" title="Story: As a user, I can have Pulp attempt use auto_retry application wide using the 'unsafe_autoretry' p... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/1">#1</a> should be still valid</p> Pulp - Story #238 (CLOSED - WONTFIX): [RFE] allow pulp-admin to set export_dir and auto_publish f...https://pulp.plan.io/issues/2382015-02-19T01:13:51Zjustin.garrison@disneyanimation.comjustin.garrison@disneyanimation.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1112859" class="external">Bugzilla Bug #1112859</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem: When trying to auto publish a repo using the export distributor there is no way to configure it except for via the API. Pulp-admin allows for --export and --export_dir but those must be run interactively and cannot be scheduled/auto published</p>
<p>Version-Release number of selected component (if applicable): 2.3</p>
<p>How reproducible: always</p>
<p>Steps to Reproduce:<br>
1. create repo<br>
2. use pulp-admin --export will only run export one time and is not scheduled. Auto publish does not have an option in pulp-admin</p>
<p>Actual results: export_dir is not configured and not saved in the database. because export_dir is not saved this causes exports to publish an iso to http(s) instead of exporting the packages to the filesystem</p>
<p>Expected results: repo exported to the filesystem after sync (auto_publish)</p>
<p>Additional info: Using the API the setting is configurable with<br>
curl -E ~/pulp.pem -k -X PUT -d '{"distributor_config": {}, "delta": {"export_dir": "/repos/", "auto_publish": true }}' <a href="https://pulp/pulp/api/v2/repositories/rhel-7-workstation-optional-rpms-x86_64/distributors/export_distributor/" class="external">https://pulp/pulp/api/v2/repositories/rhel-7-workstation-optional-rpms-x86_64/distributors/export_distributor/</a></p>
<p>the request is accepted but upon retrieving the settings the export_dir is still not set</p>
<p>curl -E ~/pulp.pem -k -X GET <a href="https://pulp/pulp/api/v2/repositories/rhel-7-workstation-optional-rpms-x86_64/distributors/export_distributor/" class="external">https://pulp/pulp/api/v2/repositories/rhel-7-workstation-optional-rpms-x86_64/distributors/export_distributor/</a></p>
<p>{<br>
"_id": {<br>
"$oid": "53a9a36abbea5770c8d1cd42"<br>
},<br>
"_ns": "repo_distributors",<br>
"auto_publish": true,<br>
"config": {<br>
"http": false,<br>
"https": false<br>
},<br>
"distributor_type_id": "export_distributor",<br>
"id": "export_distributor",<br>
"last_publish": null,<br>
"repo_id": "rhel-7-workstation-optional-rpms-x86_64",<br>
"scheduled_publishes": [],<br>
"scratchpad": null<br>
}</p> Pulp - Story #232 (CLOSED - WONTFIX): [RFE] List all uploads requests via clihttps://pulp.plan.io/issues/2322015-02-19T01:13:22Zipanova@redhat.comipanova@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1099429" class="external">Bugzilla Bug #1099429</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
At this moment it is possible to list uploads separately for rpm, iso, puppet, etc.<br>
Would be nice to have list of all uploads like it is possible in API<br>
<a href="https://pulp-dev-guide.readthedocs.org/en/latest/integration/rest-api/content/upload.html#list-all-upload-requests" class="external">https://pulp-dev-guide.readthedocs.org/en/latest/integration/rest-api/content/upload.html#list-all-upload-requests</a></p>
<p>Version-Release number of selected component (if applicable):<br>
2.4.0-0.16.beta</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1.<br>
2.<br>
3.</p>
<p>Actual results:</p>
<p>Expected results:</p>
<p>Additional info:</p> Pulp - Story #222 (CLOSED - WONTFIX): [RFE] Allow adding role in the user's creation callhttps://pulp.plan.io/issues/2222015-02-19T01:12:48Zipanova@redhat.comipanova@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1065454" class="external">Bugzilla Bug #1065454</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
Current situation requires two steps:<br>
1) create a user with POST method<br>
2) add a role to the user by making the update with the PUT method</p>
<p>Would be more convenient to specify directly roles(as an optional field) during creation of the user.<br>
As for example in repo creation call - we can create repo and add importer/distributor in one step, or update repo with these details later.</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>pulp-server-2.4.0-0.2.alpha.git.8.71f8305.fc19.noarch<br>
How reproducible:</p>
<p>Steps to Reproduce:<br>
1.<br>
2.<br>
3.</p>
<p>Actual results:<br>
role can be added only after creation call</p>
<p>Expected results:<br>
add role during create call</p>
<p>Additional info:</p> Pulp - Story #218 (CLOSED - WONTFIX): [RFE] automatic resume of interrupted uploadshttps://pulp.plan.io/issues/2182015-02-19T01:12:33Zdgregor@redhat.comdgregor@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1057250" class="external">Bugzilla Bug #1057250</a> +</span>+</p>
<p>Description of problem:</p>
<p>The pulp-admin cli has the ability to resume an interrupted upload, for example if the user hits ctrl-c. I've found that when doing many uploads, or when uploading larger files like ISOs, it's not uncommon for an upload to get interrupted due to a network hiccup. In these cases, it would be helpful in the pulp-admin client automatically attempted the resume the upload. For example, wait 15 seconds and then try again. Retry 3 times before giving up.</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> RPM Support - Story #197 (CLOSED - WONTFIX): [RFE] Add support for ftp feeds to RPM repositorieshttps://pulp.plan.io/issues/1972015-02-19T01:11:20Zjcline@redhat.comjcline@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=976032" class="external">Bugzilla Bug #976032</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem: ftp is an unsupported scheme</p>
<p>Version-Release number of selected component (if applicable): pulp-server-2.2.0-0.4.beta.fc18.noarch</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1. pulp-admin rpm repo create --repo-id=srpm --feed=<a href="ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/" class="external">ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/</a><br>
2. pulp-admin rpm repo sync run --repo-id=srpm</p>
<p>Actual results:<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Synchronizing Repository [srpm]<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>This command may be exited by pressing ctrl+c without affecting the actual<br>
operation on the server.</p>
<p>Downloading metadata...<br>
[-]<br>
... failed</p>
<p>Unsupported scheme: ftp</p>
<p>Expected results: A successful sync</p>
<p>Additional info:</p>
<p>--- Additional comment from <a href="mailto:rbarlow@redhat.com" class="email">rbarlow@redhat.com</a> at 06/19/2013 19:09:46 ---</p>
<p>It is worth noting that the ftp:// scheme was supported by Pulp 2.1.1, so this is a feature regression.</p>
<p>--- Additional comment from <a href="mailto:jskeoch@redhat.com" class="email">jskeoch@redhat.com</a> at 08/12/2013 01:36:00 ---</p>
<p>User <a href="mailto:jcline@redhat.com" class="email">jcline@redhat.com</a>'s account has been closed</p> Pulp - Story #194 (CLOSED - WONTFIX): [RFE] Add the ability to schedule publishing to the ISO sec...https://pulp.plan.io/issues/1942015-02-19T01:11:09Zrbarlow
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=971150" class="external">Bugzilla Bug #971150</a> +</span>+</p>
<p>Description of problem:</p> Pulp - Story #192 (CLOSED - WONTFIX): [RFE] pulp.bindings.repository.RepositorySearchAPI.search s...https://pulp.plan.io/issues/1922015-02-19T01:11:01Zrbarlow
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=967980" class="external">Bugzilla Bug #967980</a> +</span>+</p>
<p>Description of problem:</p>
<p>The API on the server[0] allows the caller to specify that they want importers and distributors to be included with the API call by passing "importers" and "distributors" as keys to boolean values.</p>
<p>The pulp.bindings.repository.RepositorySearchAPI.search() method only allows the specification of the search criteria, and so it is not possible to use that interface to retrieve the importers and distributors with the repositories in a single call.</p>
<p>[0] <a href="https://pulp-dev-guide.readthedocs.org/en/latest/integration/rest-api/repo/retrieval.html#advanced-search-for-repositories" class="external">https://pulp-dev-guide.readthedocs.org/en/latest/integration/rest-api/repo/retrieval.html#advanced-search-for-repositories</a></p> Pulp - Story #183 (CLOSED - WONTFIX): [RFE] pulp.plugins.config.PluginCallConfiguration.get_boole...https://pulp.plan.io/issues/1832015-02-19T01:10:28Zrbarlow
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=955369" class="external">Bugzilla Bug #955369</a> +</span>+</p>
<p>Description of problem:</p>
<p>It's a common pattern in get() methods to accept a default parameter that gets returned in the config doesn't have the requested key.</p> Pulp - Story #170 (CLOSED - WONTFIX): [RFE] Need functionality to get a list of "newest" packageshttps://pulp.plan.io/issues/1702015-02-19T00:48:32Zpaji@redhat.compaji@redhat.com
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=826743" class="external">Bugzilla Bug #826743</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
As a user of pulp I want to get a list of packages that will get installed from the repos I subscribe to.<br>
In other words <given a list of repos>-> [r1, r2, r3 ..]<br>
I 'd like an call that would return me the newest set of <package name - arch> combination. (newest as in the latest version).</p>
<p>So for example if Repo R1 had Packages with pkg.1.i386 pkg.2.x86_64 and repo R2 had pkg.2.i386<br>
I would want my call to return<br>
[pkg-2.i386, pkg-2.x86_64]</p>
<p>--- Additional comment from <a href="mailto:paji@redhat.com" class="email">paji@redhat.com</a> at 05/30/2012 21:19:15 ---</p>
<p>Feel free to email me/ comment if you have questions on this questions.</p>