Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-02-28T21:49:33ZPulp
Planio RPM Support - Issue #339 (CLOSED - WONTFIX): malformed dates are accepted for errata createhttps://pulp.plan.io/issues/3392015-02-28T21:49:33Zpthomas@redhat.com
<p>Description of problem:<br>
wrong date format is accepted for date fields --updated and --issued</p>
<p>Version-Release number of selected component (if applicable):<br>
[root@pulp-candidate scripts]# rpm -q pulp-rpm-server<br>
pulp-rpm-server-2.0.1-1.fc17.noarch<br>
[root@pulp-candidate scripts]#</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1. try to create an errata with date in the wrong format<br>
2.<br>
3.</p>
<p>Actual results:<br>
[root@pulp-candidate scripts]# pulp-admin repo uploads errata --repo-id errata_demo --erratum-id test3 --title test --description test --version 1 --release 1 --type enhancement --status final --updated 22:010 --issued 2012 --pkglist-csv package_list.csv --from <a href="mailto:pthomas@redhat.com" class="email">pthomas@redhat.com</a> --pushcount 1<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Erratum Creation<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Starting upload of selected packages. 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>Importing into the repository...<br>
... completed</p>
<p>Deleting the upload request...<br>
... completed</p>
<p>Expected results:</p>
<p>Additional info:</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=851311" class="external">Bugzilla Bug #851311</a> +</p> Pulp - Issue #338 (CLOSED - WONTFIX): ISE when descritpion or display-name has i18n characters o...https://pulp.plan.io/issues/3382015-02-28T21:48:30Zpthomas@redhat.com
<p>Description of problem:<br>
ISE when repo create is run with i18n characters for --display-name or description</p>
<p>Version-Release number of selected component (if applicable):</p>
<p>pulp-rpm-server-0.0.307-1.el6.noarch<br>
pulp-rpm-admin-client-0.0.307-1.el6.noarch</p>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br>
1. pulp-admin -u admin -p admin repo create --repo-id pulp1 --feed=<a href="http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/" class="external">http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/</a> --display-name "pulp repo display-Brasília " --description "pulp repo desc"<br>
2.<br>
3.</p>
<p>Actual results:<br>
[root@preethi-el6-pulp ~]# pulp-admin -u admin -p admin repo create --repo-id pulp1 --feed=<a href="http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/" class="external">http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/</a> --display-name "pulp repo display-Brasília " --description "pulp repo desc"<br>
An internal error occurred on the Pulp server. More information can be found in<br>
the client log file ~/.pulp/admin.log.</p>
<p>[root@preethi-el6-pulp ~]# pulp-admin -u admin -p admin repo create --repo-id pulp2 --feed=<a href="http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/" class="external">http://repos.fedorapeople.org/repos/pulp/pulp/v1/stable/6Server/x86_64/</a> --display-name "pulp repo display" --description "pulp repo desc-Brasília" An internal error occurred on the Pulp server. More information can be found in<br>
the client log file ~/.pulp/admin.log.</p>
<p>Expected results:</p>
<p>Additional info:</p>
<p>2012-06-27 11:36:07,928 16671:140082841384704: pulp.server.webservices.middleware.exception:ERROR: exception:62 Unhandled Exception<br>
Traceback (most recent call last):<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/middleware/exception.py", line 44, in <em>call</em><br>
return self.app(environ, start_response)<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/middleware/postponed.py", line 38, in <em>call</em><br>
return self.app(environ, start_response)<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 278, in wsgi<br>
result = self.handle_with_processors()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 28, in _handle_with_processors<br>
return process(self.processors)<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in process<br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 557, in processor<br>
return handler()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in <lambda><br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in process<br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 572, in processor<br>
result = handler()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in <lambda><br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 27, in process<br>
return self.handle()<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 232, in handle<br>
return self._delegate(fn, self.fvars, args)<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 413, in _delegate<br>
return f()<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 421, in <lambda><br>
f = lambda: self._delegate_sub_application(pat, what)<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 446, in _delegate_sub_application<br>
return app.handle_with_processors()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 28, in _handle_with_processors<br>
return process(self.processors)<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in process<br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 557, in processor<br>
return handler()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in <lambda><br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in process<br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 572, in processor<br>
result = handler()<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 25, in <lambda><br>
return p(lambda : process(processors))<br>
File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 27, in process<br>
return self.handle()<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 232, in handle<br>
return self._delegate(fn, self.fvars, args)<br>
File "/usr/lib/python2.6/site-packages/web/application.py", line 411, in _delegate<br>
return handle_class(cls)</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=835951" class="external">Bugzilla Bug #835951</a> +</p> Pulp - Issue #303 (CLOSED - WONTFIX): Http Event Listener: repo.publish.finish not triggered in e...https://pulp.plan.io/issues/3032015-02-25T16:10:35Zmkovacik@redhat.commkovacik@redhat.com
<p>Http repo.publish.finish Event Listener not triggered in error case: wrong distributor id was provided when issuing a repo publish call</p>
<p>Version:<br>
pulp-server-2.6.0-0.7.beta.fc21.noarch</p>
<p>How reproducible:<br>
Always, automated</p>
<p>Steps to reproduce:<br>
- create an rpm repo with a feed<br>
- create a bin at <a href="http://requestb.in/" class="external">http://requestb.in/</a><br>
- create an event listener reporting to bin.url<br>
- update the event listener to types: ['repo.publish.finish']<br>
- trigger a repo publish with a wrong/non-existent distributor id<br>
- make sure the publish task failed<br>
- check the request bin</p>
<p>Actual results:<br>
- no requests POSTed</p>
<p>Expected results:<br>
- the bin contains a request POSTed by Pulp http event listener such that<br>
- request.body:Task.state is 'error'<br>
- request.body:Task.id is publish_task.id</p>
<p>Additional Information:<br>
- pulp-automation test case: test_23_event_listener:EventListenerErrorTest.test_02_repo_publish_finish<br>
- <a href="https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py" class="external">https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py</a></p> Pulp - Issue #301 (CLOSED - WONTFIX): Http Event Listener: repo.sync.finish: task error not repor...https://pulp.plan.io/issues/3012015-02-25T15:18:39Zmkovacik@redhat.commkovacik@redhat.com
<p>Http Event Listener for the repo.sync.finish type fails to propagate related task error</p>
<p>How reproducible:<br>
Always, automated</p>
<p>Steps to reproduce:<br>
- create an rpm repo with a deliberately wrong feed url<br>
- create a bin in <a href="http://requestb.in" class="external">http://requestb.in</a><br>
- create an http event listener reporting to the bin.url<br>
- update the event listener to type: ['repo.sync.finish']<br>
- run repo sync<br>
- wait till the repo sync tasks finishes<br>
- assert the task finished with an error state<br>
- check the bin.requests</p>
<p>Actual results<br>
- bin.requests[0].body contains a running task call_report data</p>
<p>Expected results<br>
- bin.requests[0].body contains a failed-task call_report data</p>
<p>Additional information<br>
- feels like a duplicate of Issue <a class="issue tracker-1 status-9 priority-6 priority-default closed" title="Issue: Http Event Listener: repo.sync.finish fires with task in running state (CLOSED - WONTFIX)" href="https://pulp.plan.io/issues/297">#297</a><br>
- pulp-automation test case: test_23_event_listener:EventListenerErrorTest.test_01_repo_sync_finish<br>
- <a href="https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py" class="external">https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py</a></p> Pulp - Issue #299 (CLOSED - WONTFIX): Http Event Listener body: call_report should always contain...https://pulp.plan.io/issues/2992015-02-25T13:30:00Zmkovacik@redhat.commkovacik@redhat.com
<p>Since synchronous call doesn't require an event-listener call-back (it immediately gives a return value) and because all asynchronous requests are handled by Tasks in Pulp, the event listener body should always contain a valid related-task call_report.<br>
The documentation should be updated accordingly: <a href="https://pulp-dev-guide.readthedocs.org/en/latest/integration/events/http.html#body" class="external">https://pulp-dev-guide.readthedocs.org/en/latest/integration/events/http.html#body</a></p> Pulp - Issue #298 (CLOSED - WONTFIX): Http Event Listener: repo.publish.finish fires with task in...https://pulp.plan.io/issues/2982015-02-25T11:17:31Zmkovacik@redhat.commkovacik@redhat.com
<p>When a repo.publish.finish http event listener is triggered, the relevant repo publish task is still running</p>
<p>Version:<br>
pulp-server-2.6.0-0.7.beta.fc21.noarch</p>
<p>How reproducible:<br>
Always, automated</p>
<p>Steps to reproduce<br>
- create an rpm repo with feed<br>
- create an http event listener<br>
- reporting to <a href="http://requestb.in/%5C%60request_id%5C%60" class="external">http://requestb.in/\`request_id\`</a><br>
- update the event listener configuration types to: ['repo.publish.finish']<br>
- publish the repo<br>
- wait till repo publish tasks finish<br>
- inspect the request bin</p>
<p>Actual results:<br>
- the bin contains a request with a task call report in request.body such that task.state == 'running'</p>
<p>Expected results:<br>
- the bin contains a request with a task call report in request.body such that task.state == 'finished'</p>
<p>Additional Information<br>
- pulp-automation test case: test_23_event_listener:EventListenerTest.test_05_repo_publish_finish<br>
- <a href="https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py" class="external">https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py</a></p> Pulp - Issue #297 (CLOSED - WONTFIX): Http Event Listener: repo.sync.finish fires with task in ru...https://pulp.plan.io/issues/2972015-02-25T11:01:29Zmkovacik@redhat.commkovacik@redhat.com
<p>When pulp.sync.finish http event listener is triggered, the related repo sync task is still in running state</p>
<p>Version:<br>
pulp-server-2.6.0-0.7.beta.fc21.noarch</p>
<p>How reproducible:<br>
Always, automated</p>
<p>Steps to reproduce:</p>
<ol>
<li>as in the test case<br>
- create an rpm repo with feed<br>
- create http event listener<br>
- POSTing to <a href="http://requestb.in/bin_id" class="external">http://requestb.in/bin_id</a><br>
- update the event listener to types: ['repo.sync.finish']<br>
- sync the repo<br>
- wait till repo sync tasks finish<br>
- check the request bin for POSTed requests</li>
</ol>
<p>Actual Results:<br>
- the bin contains a request, request.body with a task call report such that task.state == 'running'</p>
<p>Expected Results:<br>
- the bin contains a request, request.body with a task call report such that task.state == 'finished'</p>
<p>Additional Information:<br>
pulp-automation test case: test_23_event_listener.py:EventListenerTest.test_03_repo_sync_finish<br>
<a href="https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py" class="external">https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py</a></p> Docker Support - Issue #294 (CLOSED - WONTFIX): Docker Plugin Logging Needs Improvementhttps://pulp.plan.io/issues/2942015-02-24T11:36:35ZSkullmanmminar@redhat.com
<p>When trying to debug problems of pulp_docker - last time it was validate_config failing on wrong naming (uppercase in chars in repo name) without specific error - it has really weak logging of errors compared to other pulp plugins - for example rpm.<br>
Would it be possible to add same logging capability to docker plugin - please compare:</p>
<pre><code>https://github.com/pulp/pulp_rpm/blob/master/plugins/pulp_rpm/plugins/distributors/yum/configuration.py
</code></pre>
<p>versus</p>
<pre><code>https://github.com/pulp/pulp_docker/blob/master/plugins/pulp_docker/plugins/distributors/configuration.py
</code></pre> Pulp - Issue #292 (CLOSED - WONTFIX): the setup script for a developerhttps://pulp.plan.io/issues/2922015-02-23T14:25:57Zigulina@redhat.comigulina@redhat.com
<p>Using docs [1], command</p>
<blockquote>
<blockquote>
<p>curl -O <a href="https://raw.githubusercontent.com/pulp/pulp/master/playpen/dev-setup.sh" class="external">https://raw.githubusercontent.com/pulp/pulp/master/playpen/dev-setup.sh</a> && bash -e dev-setup.sh</p>
</blockquote>
</blockquote>
<p>returns:</p>
<p>....</p>
<p>~/devel ~<br>
checking out pulp code<br>
Cloning into 'pulp'...<br>
Warning: Permanently added the RSA host key for IP address 'XXX' to the list of known hosts.<br>
Permission denied (publickey).<br>
fatal: Could not read from remote repository.</p>
<p>Please make sure you have the correct access rights<br>
and the repository exists.</p>
<p>If to follow the given docs and make a setup manually, everything is ok. Checked on f21.</p>
<p>[1] <a href="http://pulp.readthedocs.org/en/latest/dev-guide/contributing/dev_setup.html#for-the-impatient" class="external">http://pulp.readthedocs.org/en/latest/dev-guide/contributing/dev_setup.html#for-the-impatient</a></p> Docker Support - Issue #130 (CLOSED - WONTFIX): --remove-tag does not validate if that tag exists...https://pulp.plan.io/issues/1302015-01-22T20:07:32Zpthomas@redhat.com
<p>--remove-tag option in docker repo update does not validate is the tag exist or not</p>
<p>1. create repo repo<br>
2. update the repo with --remove-tag option</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo update --repo-id centos --remove-tag test_tag:511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo update --repo-id centos --remove-tag foo<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo update --repo-id centos --remove-tag cat<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo update --repo-id centos --remove-tag cat:test:tag:removal<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p> Docker Support - Issue #129 (CLOSED - WONTFIX): Docker repo create should error out when creating...https://pulp.plan.io/issues/1292015-01-22T19:03:25Zpthomas@redhat.com
<p>[root@cloud-qe-17 ~]# rpm -qa |grep pulp-docker<br>
python-pulp-docker-common-0.2.2-1.el7.noarch<br>
pulp-docker-plugins-0.2.2-1.el7.noarch<br>
pulp-docker-admin-extensions-0.2.2-1.el7.noarch<br>
[root@cloud-qe-17 ~]#</p>
<p>I used --feed -feed=<a href="https://registry.hub.docker.com/" class="external">https://registry.hub.docker.com/</a> to create a docker repo<br>
when I ran sync the sync failed. No updated the repo with --upstream-name busybox and tried the sync again. The sync ran successfully</p>
<p>root@cloud-qe-17 ~]# pulp-admin docker repo create --repo-id=synctest --feed=<a href="https://registry.hub.docker.com/" class="external">https://registry.hub.docker.com/</a><br>
Repository [synctest] successfully created</p>
<p>[root@cloud-qe-17 ~]#<br>
[root@cloud-qe-17 ~]#<br>
[root@cloud-qe-17 ~]# pulp-admin docker repo sync run --repo-id synctest<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Synchronizing Repository [synctest]<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>This command may be exited via ctrl+c without affecting the request.</p>
<p>Retrieving metadata<br>
[-]<br>
... failed<br>
NOT FOUND</p>
<p>Task Failed</p>
<p>NOT FOUND</p>
<p>[root@cloud-qe-17 ~]#<br>
[root@cloud-qe-17 ~]#<br>
[root@cloud-qe-17 ~]# pulp-admin docker repo update --repo-id=synctest --upstream-name busybox<br>
This command may be exited via ctrl+c without affecting the request.</p>
<p>[\]<br>
Running...</p>
<p>Task Succeeded</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo sync run --repo-id synctest<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Synchronizing Repository [synctest]<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>This command may be exited via ctrl+c without affecting the request.</p>
<p>Retrieving metadata<br>
[\]<br>
... completed</p>
<p>Copying units already in pulp<br>
[-]<br>
... completed</p>
<p>Downloading remote files<br>
[==================================================] 100%<br>
23 of 23 items<br>
... completed</p>
<p>Saving images and tags<br>
[-]<br>
... completed</p>
<p>Task Succeeded</p>
<p>Publishing Image Files.<br>
[==================================================] 100%<br>
10 of 10 items<br>
... completed</p>
<p>Making files available via web.<br>
[-]<br>
... completed</p>
<p>Task Succeeded</p> Docker Support - Issue #127 (CLOSED - WONTFIX): --upstream-name can be used at repo create/update...https://pulp.plan.io/issues/1272015-01-22T18:40:59Zpthomas@redhat.com
<p>[root@cloud-qe-17 ~]# rpm -qa |grep docker<br>
python-pulp-docker-common-0.2.2-1.el7.noarch<br>
docker-1.3.2-4.el7.x86_64</p>
<p>--upstream-name is an option to use with synchronization but it can be used with feedless repos</p>
<p>Synchronization<br>
--feed - URL for the upstream docker index, not including repo name<br>
--validate - if "true", the size and checksum of each synchronized file<br>
will be verified against the repo metadata<br>
--upstream-name - name of the upstream repository</p>
<p>1. create or update a feedless repo with --upstream-name<br>
2. Repo create is successful</p> Python Support - Issue #122 (CLOSED - WONTFIX): The copy command is not documentedhttps://pulp.plan.io/issues/1222015-01-22T04:38:12Zrbarlow
<p>We should document the CLI copy command.</p> Python Support - Issue #121 (CLOSED - WONTFIX): pulp_python download alias points to "/pulp/pytho...https://pulp.plan.io/issues/1212015-01-21T22:46:26Zcduryeecduryee@redhat.com
<p>I am not 100% sure but I think the "web" portion needs to be hidden, so users cannot change "/web" to "/master" in their URL and see where units are symlinked from.</p> Pulp - Issue #105 (CLOSED - DUPLICATE): repo unit association does not always use generators, lea...https://pulp.plan.io/issues/1052015-01-09T15:57:14Zcduryeecduryee@redhat.com
<p>Repo association requires the user to pass in a list of filters when working with larger sets of units[1].</p>
<p>There are multiple areas in the repo association code path that use lists instead of generators. For example, RepoUnitAssociationQueryManager.get_units() has a "as_generator" flag that is not used during associations. This is one area that needs to be fixed, but there are a few other areas as well that can cause an OOM if given a large number of units without filtered fields. See [2] for more detail.</p>
<p>Repro info to cause an OOM: sync a repo with >10K units on a machine with 4GB mem, and attempt to associate all rpm units in that repo with a new empty repo without specifying field filters.</p>
<p>[1] <a href="http://pulp.readthedocs.org/en/latest/dev-guide/integration/rest-api/content/associate.html" class="external">http://pulp.readthedocs.org/en/latest/dev-guide/integration/rest-api/content/associate.html</a><br>
[2] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1158545" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1158545</a></p>