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 - Task #6909 (CLOSED - WONTFIX): import_collection task to send filepath to galaxy...https://pulp.plan.io/issues/69092020-06-04T18:56:39Zawcrosby
<p>Currently the import_collection task sends the artifact fileobject to galaxy-importer. In galaxy-importer we want move from using the tarfile module to tar in shell.</p>
<p>We would like import_collection task to send the artifact filepath to galaxy-importer.</p>
<p>Also, currently in the fileobject we use the .storage.url property to download the artifact to a container to run "ansible-test sanity". So perhaps we can send the filepath + url instead of the opened fileobject.</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> 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> 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> 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 - Story #5038 (CLOSED - WONTFIX): As a user, I can submit one-time Remote options ...https://pulp.plan.io/issues/50382019-06-26T12:46:42Zbmbouterbmbouter@redhat.comAnsible 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> Ansible Plugin - Test #4914 (CLOSED - WONTFIX): Test upload contenthttps://pulp.plan.io/issues/49142019-06-04T19:52:30Zkersom
<p>1 - Upload content<br>
2 - Create a role from the artifact<br>
3 - Add content to a repository</p>
<p>See: <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> Ansible Plugin - Test #4912 (CLOSED - WONTFIX): [Epic] Test collection content typehttps://pulp.plan.io/issues/49122019-06-04T19:43:58Zkersom
<p>Add tests to collection content type.</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> Ansible Plugin - Test #4779 (CLOSED - WONTFIX): Test mazer 'install' won't get Content not in the...https://pulp.plan.io/issues/47792019-05-03T13:31:18Zbmbouterbmbouter@redhat.com
<p>This is the negative test related to <a href="https://pulp.plan.io/issues/4778" class="external">https://pulp.plan.io/issues/4778</a></p>
<p>Add the collection to Pulp but do <strong>not</strong> have the collection served by a Distribution.<br>
Try to have mazer install it and verify that it won't install even though the content unit is inside of Pulp (but not that Distribution).</p>
<p>This validates that content is only handed out through the correct Distributions.</p>
<p>I'm not sure if this is a very valuable test though since core is really providing this feature.</p> Ansible Plugin - Test #4777 (CLOSED - WONTFIX): Test mazer 'publish' to Pulphttps://pulp.plan.io/issues/47772019-05-03T13:27:48Zbmbouterbmbouter@redhat.com
<p>This test follows these docs: <a href="https://github.com/pulp/pulp_ansible#mazer-publish" class="external">https://github.com/pulp/pulp_ansible#mazer-publish</a></p>
<p>You should be testing against the latest checkout of <a href="https://github.com/ansible/mazer/" class="external">https://github.com/ansible/mazer/</a> and specifically the 'devel' branch.</p>
<p>1. Build the 'hello' collection like the docs say (with the mazer source, from the mazer source)<br>
2. configure mazer to point to a Distribution on Pulp. (note for this test the Distribution doesn't yet have to exist)<br>
3. mazer publish<br>
4. Verify the content is listed at <a href="http://localhost:24817/pulp/api/v3/content/ansible/collections/" class="external">http://localhost:24817/pulp/api/v3/content/ansible/collections/</a></p> Ansible Plugin - Test #4776 (CLOSED - WONTFIX): Test installing a role directly via urlhttps://pulp.plan.io/issues/47762019-05-03T13:22:40Zbmbouterbmbouter@redhat.com
<p>1. Have a role be served up by a Distribution. This is probably easiest done by uploading one, adding it to a repo version, and configuring the Distribution to serve that repo version.</p>
<p>2. Test that you can have <code>ansible-galaxy</code> client install that role directly via a pre-known URL for that unit in that distribution's url. See the example in the docs here: <a href="https://github.com/pulp/pulp_ansible#using-a-direct-path" class="external">https://github.com/pulp/pulp_ansible#using-a-direct-path</a></p> Ansible Plugin - Test #4775 (CLOSED - WONTFIX): Test Installing using the Galaxy APIhttps://pulp.plan.io/issues/47752019-05-03T13:22:35Zbmbouterbmbouter@redhat.com
<p>1. Have a role be served up by a Distribution. This is probably easiest done by uploading one, adding it to a repo version, and configuring the Distribution to serve that repo version.</p>
<p>2. Test that you can have <code>ansible-galaxy</code> client install by name (not directly by URL). You do this by configuring ansible-galaxy to point at the distribution and then installing by name. See <a href="https://github.com/pulp/pulp_ansible#using-the-pulp-galaxy-api" class="external">these docs</a> for example.</p>