Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-02-24T11:36:35ZPulp
Planio 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 #291 (CLOSED - CURRENTRELEASE): Pulp allows creation of docker repos that ...https://pulp.plan.io/issues/2912015-02-19T16:41:35Zamacdona@redhat.comaustin@redhat.com
<p>Docker has more strict requirements for repo-registry-id than pulp. It allows only [a-z0-9-_.] and a single slash.</p>
<p>Bug was originally tracked on BZ as a pulp bug.</p>
<p><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1148556" class="external">https://bugzilla.redhat.com/show_bug.cgi?id=1148556</a></p>
<p>In Pulp 2.6.0, this will respond with a pretty unhelpful PulpDataException, but this was fixed in 2.6.1</p> Python Support - Issue #154 (CLOSED - CURRENTRELEASE): pulp_python docs should use the Sphinx RTD...https://pulp.plan.io/issues/1542015-02-10T18:26:16Zbmbouterbmbouter@redhat.com
<p>When building the docs you get something that is visually different from the docs hosted at RTD. I expect the locally build html docs to use the RTD Sphinx theme if it is installed. If it is not installed it should fall back to the default sphinx theme.</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 #128 (CLOSED - CURRENTRELEASE): Running repo sync on feedless docker repos...https://pulp.plan.io/issues/1282015-01-22T18:44:12Zpthomas@redhat.com
<p>If you run repo sync on a feedless docker repo, the error message does not make any sense.</p>
<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>1. Create a feedless docker repo</p>
<p>2. Run repo sync</p>
<p>[root@cloud-qe-17 ~]# pulp-admin docker repo create --repo-id no-feed<br>
Repository [no-feed] successfully created</p>
<p>[root@cloud-qe-17 ~]#<br>
[root@cloud-qe-17 ~]# pulp-admin docker repo sync run --repo-id no-feed<br>
<span><del>--------------------------------------------------------------------</del></span><br>
Synchronizing Repository [no-feed]<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>
Invalid URL u'/v1/repositories/None/images': No schema supplied. Perhaps you<br>
meant http:///v1/repositories/None/images?</p>
<p>Task Failed</p>
<p>Invalid URL u'/v1/repositories/None/images': No schema supplied. Perhaps you<br>
meant http:///v1/repositories/None/images?</p>
<p>[root@cloud-qe-17 ~]#</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 #126 (CLOSED - CURRENTRELEASE): The docs say that we use Bugzillahttps://pulp.plan.io/issues/1262015-01-22T16:16:21Zrbarlow
<p>We should update the Python docs to reference this Redmine instance instead of Bugzilla.</p> Python Support - Issue #123 (CLOSED - CURRENTRELEASE): The documented examples use an incorrect p...https://pulp.plan.io/issues/1232015-01-22T04:41:04Zrbarlow
<p>Our documented getting started examples call an example package pulp_python_plugins when the real package is pulp-python-plugins. This means users cannot copy and paste the commands as we have written them.</p>
<p>[0] <a href="https://github.com/pulp/pulp_python/blob/master/docs/user-docs/getting_started.rst#query-packages-in-a-repository" class="external">https://github.com/pulp/pulp_python/blob/master/docs/user-docs/getting_started.rst#query-packages-in-a-repository</a></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> Docker Support - Issue #117 (CLOSED - DUPLICATE): Validation message for docker repo create does ...https://pulp.plan.io/issues/1172015-01-20T21:34:12Zpthomas@redhat.com
<p>Validation message should be clear when its failing on repo name.</p>
<p>[root@cloud-qe-17 docker]# rpm -qa pulp-server<br>
pulp-server-2.6.0-0.5.beta.el7.noarch<br>
[root@cloud-qe-17 docker]#</p>
<p>1. Create a docker repo wih the --repo-id with a capital letter</p>
<p>See the error message</p>
<p>[root@cloud-qe-17 docker]# pulp-admin docker repo create --repo-id Docker-test<br>
The server indicated one or more values were incorrect. The server provided the<br>
following error message:</p>
<pre><code>Pulp exception occurred: PulpDataException
</code></pre>
<p>More information can be found in the client log file ~/.pulp/admin.log.</p>
<p>In rpm here is the message we get</p>
<p>root@cloud-qe-17 docker]# pulp-admin rpm repo create --repo-id Docker-test.test%<br>
Validation failed for argument [--repo-id]: value must contain only letters,<br>
numbers, underscores, periods and hyphens</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> Docker Support - Issue #101 (CLOSED - CURRENTRELEASE): sync after upload clobbers parent_id and sizehttps://pulp.plan.io/issues/1012015-01-08T21:33:55Zmhrivnakmhrivnak@redhat.com
<p>If you upload a tarball of docker images to repo A and then do a sync of repo B that includes the same images, the parent_id and size attributes on the common units gets clobbered by the sync process.</p>
<ol>
<li>docker pull busybox</li>
<li>docker save busybox > bb.tar</li>
<li>pulp-admin docker repo uploads upload -f bb.tar --repo-id=repoA</li>
<li>pulp-admin docker repo images --repo-id=repoA # note that ParentId and Size are populated for some images</li>
<li>pulp-admin docker repo create --repo-id=repoB --feed=<a href="https://index.docker.io" class="external">https://index.docker.io</a> --upstream-name=busybox</li>
<li>pulp-admin docker repo images --repo-id=repoA # note that ParentId and Size are now None</li>
</ol>
<p>This was seen on both rhel7 and centos7 with both pulp 2.5.1-1 and 2.6.0-0.2.beta. Both used pulp_docker 0.2.1-1</p>