Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-12-08T21:41:37ZPulp
Planio Ansible Plugin - Test #7955 (CLOSED - WONTFIX): Load Test - Collections V3 endpointhttps://pulp.plan.io/issues/79552020-12-08T21:41:37Zfao89
<p>We need a cron job for load testing collections v3 endpoint for:</p>
<ul>
<li>12 collections</li>
<li>24 collections</li>
<li>60 collections</li>
<li>120 collections</li>
</ul>
<p>Locust reference: <a href="https://coderbook.com/@marcus/load-test-your-django-website-using-locustio/" class="external">https://coderbook.com/@marcus/load-test-your-django-website-using-locustio/</a>
github action: <a href="https://github.com/marketplace/actions/locust-load-test" class="external">https://github.com/marketplace/actions/locust-load-test</a>
CI: <a href="https://github.com/apardo04/adrianpardo.dev-react/blob/676a44b715d865496082c12752f5c18f343575d5/.github/workflows/deployment.yml#L88" class="external">https://github.com/apardo04/adrianpardo.dev-react/blob/676a44b715d865496082c12752f5c18f343575d5/.github/workflows/deployment.yml#L88</a></p> Ansible Plugin - Test #5415 (CLOSED - WONTFIX): As a user, I can publish a Collection to pulp_ans...https://pulp.plan.io/issues/54152019-09-06T19:13:04Zdaviddavis
<p>There's documentation about how to publish (or upload) a collection to pulp_ansible using the ansible-galaxy cli (formerly mazer):</p>
<p><a href="https://pulp-ansible.readthedocs.io/en/latest/workflows/index.html#collection-workflows" class="external">https://pulp-ansible.readthedocs.io/en/latest/workflows/index.html#collection-workflows</a></p>
<p>Write a test to cover this workflow.</p> Container Support - Test #5362 (CLOSED - WONTFIX): Performace testing: synchttps://pulp.plan.io/issues/53622019-08-28T10:18:34Zipanova@redhat.comipanova@redhat.com
<p>1. Deploy a local private docker registry <a href="https://docs.docker.com/registry/deploying/" class="external">https://docs.docker.com/registry/deploying/</a><br>
2a. Setup basic auth<br>
2b. Setup token auth<br>
2. Use docker fixtures to create and push content to the registry <a href="https://github.com/PulpQE/pulp-fixtures/tree/master/docker/hub" class="external">https://github.com/PulpQE/pulp-fixtures/tree/master/docker/hub</a><br>
2. Setup pulp3 with docker_plugin<br>
3. Follow workflows for syncing a repo <a href="https://pulp-docker.readthedocs.io/en/latest/workflows/sync.html#synchronize-a-repository" class="external">https://pulp-docker.readthedocs.io/en/latest/workflows/sync.html#synchronize-a-repository</a> . When creating remote in the feed specify url of the registry that has been setup in step 1</p>
<p><strong>Testing</strong><br>
When testing these scenarios should be taken into account:<br>
<a href="https://pulp.plan.io/projects/pulp/wiki/Pulp_Docker_Roadmap#MVP-2" class="external">https://pulp.plan.io/projects/pulp/wiki/Pulp_Docker_Roadmap#MVP-2</a></p> Migration Plugin - Test #5349 (CLOSED - WONTFIX): As a user, I can stop and resume migration processhttps://pulp.plan.io/issues/53492019-08-26T13:27:02Zkersom
<p>To be elaborate.</p> RPM Support - Test #5320 (CLOSED - WONTFIX): Module Streams not copying correctly with recursive ...https://pulp.plan.io/issues/53202019-08-21T12:47:54Zbherring
<ol>
<li>
<p>Create and sync the following yum repo (Source) -> <a href="https://partha.fedorapeople.org/test-repos/pteradactyl/" class="external">https://partha.fedorapeople.org/test-repos/pteradactyl/</a></p>
</li>
<li>
<p>Create another repo Dest which will serve as the destination repo</p>
</li>
<li>
<p>Go to mongo and pick up a uuid for the pteradactly:2 module stream. This stream will be copied from source to dest .</p>
</li>
<li>
<p>run the following command</p>
<pre><code>https://<fqdn>/pulp/api/v2/repositories/Dest/actions/associate/: {"source_repo_id":"Source","criteria":{"type_ids":["modulemd"],"filters":{"association":{"unit_id":{"$in":[<$MODULE UUID>]}}}},"override_config":{"recursive":true}}: {"content_type"=>"application/json", "accept"=>"application/json"}
</code></pre>
</li>
<li>
<p>pulp-admin rpm repo list. Check for the number of module mds copied over by the above call.</p>
</li>
<li>
<p>notice that with recursive set to true all the pteradactyl module streams gets copied over, instead of just pteradactly:2 and packages belonging to that</p>
</li>
<li>
<p>Behavior is similar for recursive conservative</p>
</li>
</ol> Container Support - Test #5277 (CLOSED - WONTFIX): Test - As a user I can sync a registry by whit...https://pulp.plan.io/issues/52772019-08-13T19:30:06Zkersom
<p>Motivation:</p>
<p>We're currently sync'ing some very large repos. In reality we're only interested in the particular tags but we're getting everything, which is weighing in at TBs at present and growing with each puddle for each version.</p>
<p>It would be nice to be able to limit the tags we sync.</p>
<p>Solution:</p>
<p>Provide a config on the Remote config called "whitelist_tags". This config will accept comma separated values of tags to sync.</p>
<p>When the "whitelist_tags" option is provided:</p>
<p>Pulp will sync just those tags + manifests associated with the tags and all the corresponding layers. In case of on_deman download policy layers won't be downloaded.</p>
<p>Note: If the list of tags was changed, and tag X is not wanted anymore, a manual removal of that tag X should occur in the local repo( in case repo is not in a mirror mode, mirror is not supported for now)<br>
Note: If some invalid tags provided are invalid, Pulp will only sync the available ones in the remote repo.</p>
<p>When the "whitelist_tags" option is not provided:<br>
Pulp will sync the whole repo.</p>
<p>For pulp2 implementation check <a href="https://github.com/pulp/pulp_docker/pull/241" class="external">https://github.com/pulp/pulp_docker/pull/241</a></p> Container Support - Test #5275 (CLOSED - WONTFIX): Test - As a user, I can sync from registries t...https://pulp.plan.io/issues/52752019-08-13T19:14:30Zkersom
<p>Parse 401 WWW-Authenticate response header to find out if the scheme is basic or token.</p>
<p>Sync from different registries with basicauth.</p>
<p>This pulp2 ticket might contain more info <a href="https://pulp.plan.io/issues/2956" class="external">https://pulp.plan.io/issues/2956</a></p> Ansible Plugin - Test #5269 (CLOSED - WONTFIX): Test - As a user, I have 'latest' as a boolean qu...https://pulp.plan.io/issues/52692019-08-13T18:42:11Zkersom
<p>In addition to the fields being searchable, a 'latest' parameter should be available that defaults to False. If True, it will only return the latest version when multiple versions of one Collection name are returned in the results.</p> Ansible Plugin - Test #5268 (CLOSED - WONTFIX): Test - As a user, I can upload a collection to th...https://pulp.plan.io/issues/52682019-08-13T18:38:10Zkersom
<a name="Problem"></a>
<h2 >Problem<a href="#Problem" class="wiki-anchor">¶</a></h2>
<p>Currently the one-shot uploader only is available via the galaxy bindings.</p>
<a name="Solution"></a>
<h3 >Solution<a href="#Solution" class="wiki-anchor">¶</a></h3>
<p>Add a one-shot uploader view that will use the same collection import task code. This needs to be available in the swagger API so it can be in the docs and bindings too.</p> Container Support - Test #5267 (CLOSED - WONTFIX): Test - As a user I can filter Manifests and Ma...https://pulp.plan.io/issues/52672019-08-13T18:36:40Zkersom
<p>ManifestTags will need a custom filter to allow the query through tagged_manifest.media_type.</p> Container Support - Test #5266 (CLOSED - WONTFIX): Test - Docker remote whitelist_tags can't be e...https://pulp.plan.io/issues/52662019-08-13T18:17:46Zkersom
<p>The API is giving an error when trying to enter whitelist tags as an empty string.</p> Ansible Plugin - Test #5264 (CLOSED - WONTFIX): Test - Pulp3 Ansible Collection remote doesn't se...https://pulp.plan.io/issues/52642019-08-13T18:12:22Zkersom
<p>*Steps to Reproduce:*++<br>
Steps based on httpie and jq from documentation: <a href="https://pulp-ansible.readthedocs.io/en/latest/workflows/index.html" class="external">https://pulp-ansible.readthedocs.io/en/latest/workflows/index.html</a></p>
<p>#Create 2 separate repos:<br>
http POST $BASE_ADDR/pulp/api/v3/repositories/ name=test1<br>
http POST $BASE_ADDR/pulp/api/v3/repositories/ name=test2</p>
<p>export REPO_HREF1=$(http $BASE_ADDR/pulp/api/v3/repositories/ | \<br>
jq -r '.results[] | select(.name == "test1") | ._href')</p>
<p>export REPO_HREF2=$(http $BASE_ADDR/pulp/api/v3/repositories/ | \<br>
jq -r '.results[] | select(.name == "test2") | ._href')</p>
<p>#Create collection remote:</p>
<p>http POST $BASE_ADDR/pulp/api/v3/remotes/ansible/collection/ \<br>
name='bar' \<br>
url='<a href="https://galaxy-dev.ansible.com" class="external">https://galaxy-dev.ansible.com</a>' \<br>
whitelist='newswangerd.collection_demo'</p>
<p>export REMOTE_HREF=$(http $BASE_ADDR/pulp/api/v3/remotes/ansible/collection/ | jq -r '.results[] | select(.name == "bar") | ._href')</p>
<p>#Sync both repos with the remote</p>
<p>export TASK_URL1=$(http POST $BASE_ADDR$REMOTE_HREF'sync/' repository=$REPO_HREF1 \<br>
| jq -r '.task')</p>
<p>export TASK_URL2=$(http POST $BASE_ADDR$REMOTE_HREF'sync/' repository=$REPO_HREF2 \<br>
| jq -r '.task')</p>
<p>#Notice that a new repo version is created by 1st task but none by the 2nd.</p>
<p>http $BASE_ADDR$TASK_URL1</p>
<p>http $BASE_ADDR$TASK_URL2</p>
<p>*<strong>*</strong>*********************************************************</p>
<p>I tried with a second remote pointing to the same URL and with the same whitelist and it doesn't seem to create a repo version either.</p> Container Support - Test #5260 (CLOSED - WONTFIX): Test - As a user, I can filter Manifests and M...https://pulp.plan.io/issues/52602019-08-13T17:35:25Zkersom
<p>For example, I would like to retrieve all v1 and v2 manifests without any manifest lists.</p> Ansible Plugin - Test #5257 (CLOSED - WONTFIX): Test - As a user, I can have fulltext search on C...https://pulp.plan.io/issues/52572019-08-13T14:46:17Zkersom
<p>A fulltext search should be added using examples here: <a href="https://github.com/abarto/full_text_search_drf" class="external">https://github.com/abarto/full_text_search_drf</a></p> Ansible Plugin - Test #4976 (CLOSED - WONTFIX): Collection - Test if creating duplicate content r...https://pulp.plan.io/issues/49762019-06-14T18:47:29Zkersom
<ul>
<li>Evaluate if we already have similar tests in place.</li>
<li>Create duplicate content</li>
<li>Assert that an HTTP Bad Request - 400 was raised</li>
<li>Assert that an error (e.g. "There is already a file content unit with relativepath 'foo.tar.gz' and artifact '/pulp/api/v3/artifacts/1/'.") is returned</li>
</ul>