Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-10-05T13:56:02ZPulp
Planio Ansible Plugin - Task #9489 (MODIFIED): Make use of shared_resources in sync and copy jobshttps://pulp.plan.io/issues/94892021-10-05T13:56:02ZmdellwegAnsible Plugin - Issue #8923 (CLOSED - CURRENTRELEASE): Backport streamed collection endpoints to...https://pulp.plan.io/issues/89232021-06-18T18:26:07Zrochacbruno
<p>Backport the PRS</p>
<p><a href="https://github.com/pulp/pulp_ansible/pull/573" class="external">https://github.com/pulp/pulp_ansible/pull/573</a></p>
<p><a href="https://github.com/pulp/pulp_ansible/pull/562" class="external">https://github.com/pulp/pulp_ansible/pull/562</a></p>
<p>So galaxy_ng can use the optimized sync</p> Ansible Plugin - Issue #6855 (CLOSED - CURRENTRELEASE): Automation hub tarballs have invalid name...https://pulp.plan.io/issues/68552020-05-28T15:27:44Zosapryki
<p>Collection tarballs downloaded from Automation Hub using the download button have their names formatted with periods as <code><namespace>.<collection>.<version></code> when they should be formatted with dashes as <code><namespace>-<collection>-<version></code>.</p> Ansible Plugin - Issue #5358 (CLOSED - CURRENTRELEASE): Galaxy API v3 collection upload should cr...https://pulp.plan.io/issues/53582019-08-27T12:45:14ZosaprykiAnsible Plugin - Issue #5357 (CLOSED - CURRENTRELEASE): Galaxy API v3 collection upload should re...https://pulp.plan.io/issues/53572019-08-27T12:42:50ZosaprykiAnsible Plugin - Issue #5301 (CLOSED - CURRENTRELEASE): Add endpoints for CollectionImportshttps://pulp.plan.io/issues/53012019-08-19T16:38:06Zosapryki
<ul>
<li>Add Galaxy endpoint to get specific import task details</li>
<li>Add generic ViewSet for pulp_ansible API.</li>
</ul> Ansible Plugin - Task #5300 (CLOSED - CURRENTRELEASE): Add data models for tracking collection im...https://pulp.plan.io/issues/53002019-08-19T16:36:08ZosaprykiAnsible Plugin - Task #5287 (CLOSED - CURRENTRELEASE): Add certified status and related endpoint ...https://pulp.plan.io/issues/52872019-08-15T16:04:49ZosaprykiAnsible Plugin - Issue #5226 (CLOSED - CURRENTRELEASE): Migration 0004_add_fulltext_search_indexe...https://pulp.plan.io/issues/52262019-08-06T20:09:00Zosapryki
<p>Migration <code>0004_add_fulltext_search_indexes</code> fails with the following exception when trying to execute against database table that actually contains data.</p>
<pre><code>Traceback (most recent call last):
File "/venv/bin/django-admin", line 11, in <module>
sys.exit(execute_from_command_line())
File "/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/venv/lib64/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
fake_initial=fake_initial,
File "/venv/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/venv/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/venv/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
state = migration.apply(state, schema_editor)
File "/venv/lib64/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/venv/lib64/python3.6/site-packages/django/db/migrations/operations/special.py", line 105, in database_forwards
self._run_sql(schema_editor, self.sql)
File "/venv/lib64/python3.6/site-packages/django/db/migrations/operations/special.py", line 130, in _run_sql
schema_editor.execute(statement, params=None)
File "/venv/lib64/python3.6/site-packages/django/db/backends/base/schema.py", line 137, in execute
cursor.execute(sql, params)
File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 99, in execute
return super().execute(sql, params)
File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/venv/lib64/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 82, in _execute
return self.cursor.execute(sql)
django.db.utils.ProgrammingError: more than one row returned by a subquery used as an expression
</code></pre>
<p>The SQL query that causes this exception is this:</p>
<pre><code> UPDATE ansible_collectionversion AS c
SET search_vector = (
SELECT
setweight(to_tsvector(coalesce(namespace,'')), 'A')
|| setweight(to_tsvector(coalesce(name, '')), 'A')
|| (
SELECT
setweight(to_tsvector(
coalesce(string_agg("ansible_tag"."name", ' '), '')
), 'B')
FROM
"ansible_tag" INNER JOIN "ansible_collectionversion_tags" ON ("ansible_tag"."_id" = "ansible_collectionversion_tags"."tag_id")
)
|| (
SELECT
setweight(to_tsvector(
coalesce(string_agg(cvc ->> 'name', ' '), '')
), 'C')
FROM jsonb_array_elements(cv.contents) AS cvc
)
|| setweight(to_tsvector(coalesce(description, '')), 'D')
FROM ansible_collectionversion cv
)
</code></pre> Ansible Plugin - Task #5225 (CLOSED - CURRENTRELEASE): Implement collections and collection versi...https://pulp.plan.io/issues/52252019-08-06T11:03:04ZosaprykiAnsible Plugin - Task #5224 (CLOSED - CURRENTRELEASE): Implement custom pagination and error hand...https://pulp.plan.io/issues/52242019-08-06T11:02:10ZosaprykiAnsible Plugin - Task #5223 (CLOSED - CURRENTRELEASE): Add highest version mark to CollectionVers...https://pulp.plan.io/issues/52232019-08-06T11:01:02ZosaprykiAnsible Plugin - Story #5105 (CLOSED - CURRENTRELEASE): Implement advanced collection modelshttps://pulp.plan.io/issues/51052019-07-10T12:37:43Zosapryki
<p>Update collection models to store metadata retrieved from collection as a result of artifact importing and linting process.<br>
Collection models should be match when possible existing Galaxy collection models.</p> Ansible Plugin - Task #3914 (CLOSED - CURRENTRELEASE): Port pulp_ansible to use DeclarativeVersionhttps://pulp.plan.io/issues/39142018-08-13T21:08:58Zbmbouterbmbouter@redhat.com
<a name="Overview"></a>
<h2 >Overview<a href="#Overview" class="wiki-anchor">¶</a></h2>
<p>Now that DeclarativeVersion is available the pulp_ansible plugin can port onto it. The progress reporting names will change, but otherwise this change will not be noticable to users, except maybe faster performance.</p>
<a name="Implementation"></a>
<h2 >Implementation<a href="#Implementation" class="wiki-anchor">¶</a></h2>
<p>The implementation will have two main parts, a metadata downloading page-by-page part, and then an object building part (i.e. Content unit, Artifact, DeclarativeArtifact, and DeclarativeContent). The metadata downloading part is the complicated part because in the paginated API you want several downloads running concurrently.</p>
<p>This is currently done in the pulp_ansible code. A master list is built here: <a href="https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L153" class="external">https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L153</a> Then 20 outstanding downloads happen here: <a href="https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L155-L158" class="external">https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L155-L158</a></p>
<p>Then the "new_roles" data from a fetched page is parsed here <a href="https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L168" class="external">https://github.com/pulp/pulp_ansible/blob/master/pulp_ansible/app/tasks/synchronizing.py#L168</a> This is where the Content units and Artifact objects should be encapsulated in DeclarativeContent and DeclarativeArtifact objects respectively. This is similar to what pulp_file does: <a href="https://github.com/pulp/pulp_file/blob/master/pulp_file/app/tasks/synchronizing.py#L74-L75" class="external">https://github.com/pulp/pulp_file/blob/master/pulp_file/app/tasks/synchronizing.py#L74-L75</a></p> Ansible Plugin - Issue #3898 (CLOSED - CURRENTRELEASE): Filters inherit from a Django's FilterSet...https://pulp.plan.io/issues/38982018-08-02T15:13:08Zvdusek
<p>AnsibleRoleFilter and AnsibleRoleVersionFilter inherit from Django's filterset.FilterSet class not from our BaseFilterSet. I suppose this could cause problems in generating documentation.</p>