Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-09-17T14:10:06ZPulp
Planio Pulp - Issue #9421 (MODIFIED): Add support for sslmode to settings in pulp and pulp-operator.https://pulp.plan.io/issues/94212021-09-17T14:10:06Zbenthomasson
<p>In order to run AAP on Azure I need to enable the sslmode option for the database connection for automation hub.</p>
<p>Automation Hub runs as a django app and so needs a DATABASES configuration like this:</p>
<pre><code class="python syntaxhl" data-language="python"><span class="n">DATABASES</span> <span class="o">=</span> <span class="p">{</span>
<span class="s">'default'</span><span class="p">:</span> <span class="p">{</span>
<span class="s">'ENGINE'</span><span class="p">:</span> <span class="s">'django.db.backends.postgresql'</span><span class="p">,</span>
<span class="s">'NAME'</span><span class="p">:</span> <span class="s">"db_name"</span><span class="p">,</span>
<span class="s">'USER'</span><span class="p">:</span> <span class="s">"db_username"</span><span class="p">,</span>
<span class="s">'PASSWORD'</span><span class="p">:</span> <span class="s">"db_password"</span><span class="p">,</span>
<span class="s">'HOST'</span><span class="p">:</span> <span class="s">"db_host"</span><span class="p">,</span>
<span class="s">'OPTIONS'</span><span class="p">:</span> <span class="p">{</span><span class="s">'sslmode'</span><span class="p">:</span> <span class="s">'require'</span><span class="p">},</span>
<span class="p">},</span>
<span class="p">}</span>
</code></pre>
<p>I am using the pulp-operator to install galaxy_ng and I would like the pulp-operator to look for this option in the databases secret:</p>
<pre><code class="yaml syntaxhl" data-language="yaml">
<span class="nn">---</span>
<span class="na">apiVersion</span><span class="pi">:</span> <span class="s">v1</span>
<span class="na">kind</span><span class="pi">:</span> <span class="s">Secret</span>
<span class="na">metadata</span><span class="pi">:</span>
<span class="na">name</span><span class="pi">:</span> <span class="s">galaxy-pulp-postgres-configuration</span>
<span class="na">namespace</span><span class="pi">:</span> <span class="s">default</span>
<span class="na">stringData</span><span class="pi">:</span>
<span class="na">host</span><span class="pi">:</span> <span class="s">postgres</span>
<span class="na">port</span><span class="pi">:</span> <span class="s2">"</span><span class="s">5432"</span>
<span class="na">database</span><span class="pi">:</span> <span class="s">pulp</span>
<span class="na">username</span><span class="pi">:</span> <span class="s">pulp</span>
<span class="na">password</span><span class="pi">:</span> <span class="s">XXX</span>
<span class="na">sslmode</span><span class="pi">:</span> <span class="s">require</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">unmanaged</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">Opaque</span>
</code></pre> Pulp - Issue #9395 (CLOSED - CURRENTRELEASE): RemoteArtifacts are not being saved properlyhttps://pulp.plan.io/issues/93952021-09-14T03:24:43Zdalleydalley@redhat.com
<p>This is the result of a long discussion on the Katello forums: <a href="https://community.theforeman.org/t/katello-4-1-2-1-404-error-through-content-proxy-due-to-incorrect-location-href/24812/26?u=dralley" class="external">https://community.theforeman.org/t/katello-4-1-2-1-404-error-through-content-proxy-due-to-incorrect-location-href/24812/26?u=dralley</a></p>
<p>TL;DR if you sync a repository on-demand multiple times against different repos, only the first set of RemoteArtifacts is saved. If the layout of the repository changes or the repository disappears, all of these URLs get broken, and the RemoteArtifacts are thus broken even if they were supposed to have multiple different potential sources.</p>
<p>I've confirmed this by syncing a single repository, changing the layout of that repository, and resyncing. Only the original RemoteArtifact will exist and the new ones will not. A script is attached to demonstrate this (if you look in the DB afterwards)</p>
<p>This is an especially severe issue because "metadata mirroring" and standard syncs have entirely different layouts, so re-publishing a mirrored repository or mirroring it after having otherwise not been doing so results in broken repositories due to all of the URLs changing.</p> Pulp - Issue #9269 (CLOSED - CURRENTRELEASE): Allow content types that declare their own custom m...https://pulp.plan.io/issues/92692021-08-21T17:15:36Zdalleydalley@redhat.com
<p>Content subclasses that declare their own custom managers don't have access to touch() functionality, we need to export it through the API so that they can subclass it.</p> Pulp - Issue #8603 (CLOSED - CURRENTRELEASE): possible tasking race condition: update or delete ...https://pulp.plan.io/issues/86032021-04-20T19:30:22Zjsherril@redhat.comjsherril@redhat.com
<p>With pulpcore 3.11.0</p>
<pre><code>pulp [34656514-03a4-4255-b3b7-8986492b87b1]: rq.worker:ERROR: Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
psycopg2.errors.ForeignKeyViolation: update or delete on table "core_reservedresource" violates foreign key constraint "core_taskreservedres_resource_id_ee0b7c62_fk_core_rese" on table "core_taskreservedresource"
DETAIL: Key (pulp_id)=(c0b7db83-401e-4a46-8d9e-07f5ab70de1e) is still referenced from table "core_taskreservedresource".
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/rq/worker.py", line 984, in perform_job
started_job_registry=started_job_registry)
File "/usr/lib/python3.6/site-packages/pulpcore/tasking/worker.py", line 146, in handle_job_success
task.release_resources()
File "/usr/lib/python3.6/site-packages/pulpcore/app/models/task.py", line 430, in release_resources
reservation.delete()
File "/usr/lib/python3.6/site-packages/django_lifecycle/mixins.py", line 146, in delete
value = super().delete(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 922, in delete
return collector.delete()
File "/usr/lib/python3.6/site-packages/django/db/models/deletion.py", line 318, in delete
sender=model, instance=obj, using=self.using
File "/usr/lib/python3.6/site-packages/django/db/transaction.py", line 240, in __exit__
connection.commit()
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 262, in commit
self._commit()
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
File "/usr/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
django.db.utils.IntegrityError: update or delete on table "core_reservedresource" violates foreign key constraint "core_taskreservedres_resource_id_ee0b7c62_fk_core_rese" on table "core_taskreservedresource"
DETAIL: Key (pulp_id)=(c0b7db83-401e-4a46-8d9e-07f5ab70de1e) is still referenced from table "core_taskreservedresource".
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
psycopg2.errors.ForeignKeyViolation: update or delete on table "core_reservedresource" violates foreign key constraint "core_taskreservedres_resource_id_ee0b7c62_fk_core_rese" on table "core_taskreservedresource"
DETAIL: Key (pulp_id)=(c0b7db83-401e-4a46-8d9e-07f5ab70de1e) is still referenced from table "core_taskreservedresource".
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/rq/worker.py", line 984, in perform_job
started_job_registry=started_job_registry)
File "/usr/lib/python3.6/site-packages/pulpcore/tasking/worker.py", line 146, in handle_job_success
task.release_resources()
File "/usr/lib/python3.6/site-packages/pulpcore/app/models/task.py", line 430, in release_resources
reservation.delete()
File "/usr/lib/python3.6/site-packages/django_lifecycle/mixins.py", line 146, in delete
value = super().delete(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/django/db/models/base.py", line 922, in delete
return collector.delete()
File "/usr/lib/python3.6/site-packages/django/db/models/deletion.py", line 318, in delete
sender=model, instance=obj, using=self.using
File "/usr/lib/python3.6/site-packages/django/db/transaction.py", line 240, in __exit__
connection.commit()
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 262, in commit
self._commit()
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
File "/usr/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/lib/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
return self.connection.commit()
django.db.utils.IntegrityError: update or delete on table "core_reservedresource" violates foreign key constraint "core_taskreservedres_resource_id_ee0b7c62_fk_core_rese" on table "core_taskreservedresource"
DETAIL: Key (pulp_id)=(c0b7db83-401e-4a46-8d9e-07f5ab70de1e) is still referenced from table "core_taskreservedresource".
pulp [None]: rq.worker:INFO: 28341@pipe-up-katello-proxy-nightly-centos7.n60.example.com: a9f5653c-8d52-47ea-b36b-52f86d91e9a3
</code></pre> Debian Support - Issue #8307 (CLOSED - CURRENTRELEASE): Signing Service is broken by pulpcore changehttps://pulp.plan.io/issues/83072021-02-25T12:30:31Zquba42
<p>I need to implement usage of the new Signing Service fields from pulpcore and fix the tests.</p> Pulp - Issue #7754 (CLOSED - CURRENTRELEASE): PostgreSQL extension uuid-ossp is missing in pulp/p...https://pulp.plan.io/issues/77542020-10-27T14:22:55Zosapryki
<p>Automation Hub requires PostgreSQL extension "uuid-ossp" to perform a data migration <a href="https://github.com/ansible/galaxy_ng/pull/528" class="external">https://github.com/ansible/galaxy_ng/pull/528</a>, however Travis CI fails with the following error:</p>
<pre><code>django.db.utils.OperationalError: could not open extension control file "/usr/share/pgsql/extension/uuid-ossp.control": No such file or directory
</code></pre>
<p>This error occurs because <code>pulp/pulp-ci</code> image has a PostgreSQL installed without compiled standard extensions (specifically "uuid-ossp").</p> Pulp - Issue #7676 (CLOSED - CURRENTRELEASE): django-cleanup can silently delete files being used...https://pulp.plan.io/issues/76762020-10-08T14:15:28Zdalleydalley@redhat.com
<pre><code>Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp: pulp_rpm.app.tasks.publishing:INFO: Publishing: repository=centos8-baseos, version=1
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp: rq.worker:ERROR: Traceback (most recent call last):
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py", line 936, in perform_job
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: rv = job.perform()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 684, in perform
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: self._result = self._execute()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 690, in _execute
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return self.func(*self.args, **self.kwargs)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/tasks/migrate.py", line 142, in migrate_from_pulp2
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: create_repoversions_publications_distributions(plan)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 323, in create_repoversions_publications_distributions
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: task_func(*task_args)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 270, in complex_repo_migration
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: migrated_repo.pulp3_repository_version
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 391, in migrate_repo_distributor
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp2dist, repo_version)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/plugin/rpm/repository.py", line 74, in migrate_to_pulp3
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: publish(repo_version.pk, checksum_types=checksum_types)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 283, in publish
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: publication_data.populate()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 224, in populate
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: self.handle_sub_repos(distribution_tree)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 165, in handle_sub_repos
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: artifact_file = storage.open(original_treeinfo_content_artifact.artifact.file.name)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/files/storage.py", line 36, in open
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return self._open(name, mode)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/files/storage.py", line 224, in _open
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return File(open(self.path(name), mode))
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/pulp/artifact/48/66eceaf78ffabb1d25774932085c6653f9f654411d7669db7b91e2ef0fd2a3'
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: Traceback (most recent call last):
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py", line 936, in perform_job
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: rv = job.perform()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 684, in perform
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: self._result = self._execute()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 690, in _execute
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return self.func(*self.args, **self.kwargs)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/tasks/migrate.py", line 142, in migrate_from_pulp2
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: create_repoversions_publications_distributions(plan)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 323, in create_repoversions_publications_distributions
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: task_func(*task_args)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 270, in complex_repo_migration
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: migrated_repo.pulp3_repository_version
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/migration.py", line 391, in migrate_repo_distributor
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp2dist, repo_version)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/plugin/rpm/repository.py", line 74, in migrate_to_pulp3
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: publish(repo_version.pk, checksum_types=checksum_types)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 283, in publish
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: publication_data.populate()
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 224, in populate
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: self.handle_sub_repos(distribution_tree)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/home/vagrant/devel/pulp_rpm/pulp_rpm/app/tasks/publishing.py", line 165, in handle_sub_repos
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: artifact_file = storage.open(original_treeinfo_content_artifact.artifact.file.name)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/files/storage.py", line 36, in open
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return self._open(name, mode)
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/files/storage.py", line 224, in _open
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: return File(open(self.path(name), mode))
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/pulp/artifact/48/66eceaf78ffabb1d25774932085c6653f9f654411d7669db7b91e2ef0fd2a3'
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp: rq.worker:INFO: 26855@pulp2-nightly-pulp3-source-centos7.localhost.example.com: c009a655-bb3e-4665-9b2e-b3100b82b060
Oct 08 13:30:37 pulp2-nightly-pulp3-source-centos7.localhost.example.com rq[26855]: pulp: rq.worker:INFO: 26855@pulp2-nightly-pulp3-source-centos7.localhost.example.com: Job OK (c009a655-bb3e-4665-9b2e-b3100b82b060)
</code></pre> Pulp - Issue #7663 (CLOSED - CURRENTRELEASE): SELinux policies not being applied when using RPM b...https://pulp.plan.io/issues/76632020-10-07T11:16:21Zspredzy
<p>As a user I am deploying pulpcore using the pulp_installer (3.7.1) and the upstream packages located at <a href="https://yum.theforeman.org/pulpcore/3.7/el7/x86_64/" class="external">https://yum.theforeman.org/pulpcore/3.7/el7/x86_64/</a></p>
<p>After installation the services are started as <code>unconfined_service_t</code> rather than <code>pulpcore_t</code> (as per the pulpcore-selinux definition <a href="https://github.com/pulp/pulpcore-selinux/blob/master/pulpcore.te#L8" class="external">https://github.com/pulp/pulpcore-selinux/blob/master/pulpcore.te#L8</a>)</p>
<pre><code>[root@localhost vagrant]# rpm -qa | grep pulpcore-selinux
pulpcore-selinux-1.1.1-1.el7.x86_64
[root@localhost vagrant]# semodule -l | grep pulp
pulpcore 1.1.1
pulpcore_port 1.1.1
pulpcore_rhsmcertd 1.1.1
[root@localhost vagrant]# ps -Z fauxwww | grep pulpcore-api
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 3533 0.0 0.1 12532 984 pts/1 S+ 11:07 0:00 \_ grep --color=auto pulpcore-api
system_u:system_r:unconfined_service_t:s0 pulp 2986 0.0 1.0 122984 5220 ? Ss 09:29 0:02 /usr/bin/python3 /usr/bin/gunicorn pulpcore.app.wsgi:application --bind unix:/var/run/pulpcore-api/pulpcore-api.sock --workers 4 --access-logfile -
system_u:system_r:unconfined_service_t:s0 pulp 2989 0.0 6.9 276252 34836 ? S 09:29 0:01 \_ /usr/bin/python3 /usr/bin/gunicorn pulpcore.app.wsgi:application --bind unix:/var/run/pulpcore-api/pulpcore-api.sock --workers 4 --access-logfile -
system_u:system_r:unconfined_service_t:s0 pulp 2991 0.0 6.9 276252 34500 ? S 09:29 0:01 \_ /usr/bin/python3 /usr/bin/gunicorn pulpcore.app.wsgi:application --bind unix:/var/run/pulpcore-api/pulpcore-api.sock --workers 4 --access-logfile -
system_u:system_r:unconfined_service_t:s0 pulp 2992 0.0 6.5 276252 32848 ? S 09:29 0:01 \_ /usr/bin/python3 /usr/bin/gunicorn pulpcore.app.wsgi:application --bind unix:/var/run/pulpcore-api/pulpcore-api.sock --workers 4 --access-logfile -
system_u:system_r:unconfined_service_t:s0 pulp 2995 0.0 6.1 276344 30620 ? S 09:29 0:01 \_ /usr/bin/python3 /usr/bin/gunicorn pulpcore.app.wsgi:application --bind unix:/var/run/pulpcore-api/pulpcore-api.sock --workers 4 --access-logfile -
[root@localhost vagrant]#
</code></pre>
<p>Expected behavior is to have everything properly labeled</p> Debian Support - Issue #7190 (CLOSED - CURRENTRELEASE): Pulp 3 - pulp-deb : APT client installing...https://pulp.plan.io/issues/71902020-07-22T14:11:24Zswisscom
<p>Dear support,</p>
<p>We have the same issue than reported in <a href="https://pulp.plan.io/issues/6982" class="external">https://pulp.plan.io/issues/6982</a> but for field Multi-Arch (was fixed for field Installed-Size in <a href="https://github.com/pulp/pulp_deb/pull/184" class="external">https://github.com/pulp/pulp_deb/pull/184</a>)</p>
<p>Would it be possible to fix missing Multi-Arch field ?
And in addition if possible not put SHA1 field in Packages file when SHA1 value is empty...</p>
<p>Pulp components version :</p>
<pre><code class="text syntaxhl" data-language="text">(pulp) -bash-4.2$ pip list | grep pulp
pulp-deb 2.6.0b1.dev0 /var/lib/pulp/pulp_deb
pulp-rpm 3.4.2
pulpcore 3.5.0
</code></pre>
<p>Thanks in advance</p> Debian Support - Issue #6982 (CLOSED - CURRENTRELEASE): Pulp 3 - pulp-deb : APT client installing...https://pulp.plan.io/issues/69822020-06-16T12:46:52Zswisscom
<p>Dear support team,
When setting up APT client to connect to Pulp to get it's content, I discovered that it installs the same patches again and again. Like if I run twice "apt-get upgrade -y", it will install 339 packages the two times.</p>
<p>The issue is due to the fact the "Installed-Size" field is missing in the Packages file produced by Pulp. "Installed-Size" is one of the mandatory fields, that is used by APT client to check if the patch is already installed or not.</p>
<p>Mpore information here : <a href="https://github.com/Debian/apt/issues/23" class="external">https://github.com/Debian/apt/issues/23</a>
The following fields must be the same in the Packages file and /var/lib/dpkg status: "Installed-Size",
"Depends", "Pre-Depends", "Conflicts", "Breaks", "Replaces". All spaces are ignored, all values are transformed to lowercase, and <= and >= are normalized into < and >.</p>
<p>Would it be possible to fix this issue ?</p>
<p>Thanks a lot</p> Debian Support - Issue #6876 (CLOSED - CURRENTRELEASE): Pulp 3 - pulp-deb : Wrong paths in Releas...https://pulp.plan.io/issues/68762020-06-02T10:23:11Zswisscom
<p>Dear support team,</p>
<p>I discovered a major issue in the Release file produced by pulp-deb publications.
The paths are wrong, because it must be relative from the place where the Release file is. With wrong path in Release file, the repo cannot be used (apt client do not see any package comin</p>
<p>Example of what I see in Release file produced by Pulp :</p>
<pre><code class="python syntaxhl" data-language="python"><span class="n">MD5sum</span><span class="p">:</span>
<span class="n">aa84d85627f4b4d1e1d8072b238150ca</span> <span class="mi">39099687</span> <span class="n">dists</span><span class="o">/</span><span class="n">buster</span><span class="o">/</span><span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">s390x</span><span class="o">/</span><span class="n">Packages</span>
<span class="mi">422</span><span class="n">f6f847b971d36d26d724d04e8a0f2</span> <span class="mi">11994723</span> <span class="n">dists</span><span class="o">/</span><span class="n">buster</span><span class="o">/</span><span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">s390x</span><span class="o">/</span><span class="n">Packages</span><span class="p">.</span><span class="n">gz</span>
<span class="mf">4e01</span><span class="n">fb37905070bf47a186b9321aa507</span> <span class="mi">39689978</span> <span class="n">dists</span><span class="o">/</span><span class="n">buster</span><span class="o">/</span><span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">ppc64el</span><span class="o">/</span><span class="n">Packages</span>
<span class="mi">15681</span><span class="n">a4fb0e26463cd7eca6e4c8c4082</span> <span class="mi">12128141</span> <span class="n">dists</span><span class="o">/</span><span class="n">buster</span><span class="o">/</span><span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">ppc64el</span><span class="o">/</span><span class="n">Packages</span><span class="p">.</span><span class="n">gz</span>
<span class="mi">57439</span><span class="n">b8db44e619293e6df3bc0666de0</span> <span class="mi">39371394</span> <span class="n">dists</span><span class="o">/</span><span class="n">buster</span><span class="o">/</span><span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">mipsel</span><span class="o">/</span><span class="n">Packages</span>
</code></pre>
<p>What it must be :</p>
<pre><code class="python syntaxhl" data-language="python"><span class="n">MD5sum</span><span class="p">:</span>
<span class="n">aa84d85627f4b4d1e1d8072b238150ca</span> <span class="mi">39099687</span> <span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">s390x</span><span class="o">/</span><span class="n">Packages</span>
<span class="mi">422</span><span class="n">f6f847b971d36d26d724d04e8a0f2</span> <span class="mi">11994723</span> <span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">s390x</span><span class="o">/</span><span class="n">Packages</span><span class="p">.</span><span class="n">gz</span>
<span class="mf">4e01</span><span class="n">fb37905070bf47a186b9321aa507</span> <span class="mi">39689978</span> <span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">ppc64el</span><span class="o">/</span><span class="n">Packages</span>
<span class="mi">15681</span><span class="n">a4fb0e26463cd7eca6e4c8c4082</span> <span class="mi">12128141</span> <span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">ppc64el</span><span class="o">/</span><span class="n">Packages</span><span class="p">.</span><span class="n">gz</span>
<span class="mi">57439</span><span class="n">b8db44e619293e6df3bc0666de0</span> <span class="mi">39371394</span> <span class="n">main</span><span class="o">/</span><span class="n">binary</span><span class="o">-</span><span class="n">mipsel</span><span class="o">/</span><span class="n">Packages</span>
</code></pre>
<p>Example of a working Release file : <a href="http://ftp.debian.org/debian/dists/buster/Release" class="external">http://ftp.debian.org/debian/dists/buster/Release</a></p>
<p>FYI : I already applied this fix : <a href="https://github.com/pulp/pulp_deb/pull/173" class="external">https://github.com/pulp/pulp_deb/pull/173</a></p>
<p>Thanks for your help</p> Pulp - Issue #6154 (CLOSED - CURRENTRELEASE): Redirect to S3 in pulp-content-app is broken in 3.1.0https://pulp.plan.io/issues/61542020-02-13T14:29:13Zosapryki
<p>pulp-content-app returns redirect to invalid S3 URL:</p>
<pre><code>https://bucket.s3.amazonaws.com/artifact/xx/xxx?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=********&X-Amz-Date=20200213T141229Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=********?response-content-disposition=attachment;+filename=pulp-artifact-filename
</code></pre>
<p><code>response-content-disposition</code> is attached to the URL that already has query string which gives as a result invalid URL.</p>
<p>Please refer to for the correct example of setting Response-Content-Disposition parameter with django-storages:</p>
<p><a href="https://github.com/ansible/galaxy/blob/devel/galaxy/api/download/views.py#L64" class="external">https://github.com/ansible/galaxy/blob/devel/galaxy/api/download/views.py#L64</a></p> Pulp - Issue #5673 (CLOSED - CURRENTRELEASE): Resource reservations are not cleaned up if worker ...https://pulp.plan.io/issues/56732019-11-06T17:29:15Zosapryki
<p>It pulp worker is killed while executing task that has reserved resources, resources are not cleaned up.<br>
All subsequent task that use any of the reserved resources are assigned to the same worker (which is dead).</p>
<p>Steps to reproduce:</p>
<p>1. Spawn import_collection task from pulp_ansible (T1).<br>
2. While task is running kill worker (W1).<br>
3. Start another worker (W2)<br>
4. Spawn import_collection task from pulp_ansible (T2)</p>
<p>Expected behavior:</p>
<p>Task T2 is assigned on worker W2 or Cancelled if assigned on W1 before cleanup is performed.</p>
<p>Actual behavior:</p>
<p>Task T2 is assigned on worker W1 and remains in waiting state forever.<br>
Resources are not cleaned up.</p>
<p>Environment:</p>
<p>pulpcore + pulp_ansible.<br>
1 worker</p> Ansible Plugin - Issue #5571 (CLOSED - CURRENTRELEASE): Add the ability to filter collection vers...https://pulp.plan.io/issues/55712019-10-14T20:13:14Znewswangerd
<p>We need a parameter on `/pulp/api/v3/content/ansible/collection_versions/` that allows for us to filter collection versions by tag, such that we can specify `tags=?network,cloud` and get a list of collection versions that have the network AND cloud tags.</p> Debian Support - Issue #5377 (CLOSED - CURRENTRELEASE): Cannot modify, delete, or duplicate contenthttps://pulp.plan.io/issues/53772019-08-30T18:52:56Zjaymzh
<p>Once an artifact has been made into apt content, that content cannot be modified or deleted. Further, you can't work around this by creating new content because multiple contents cannot point to the same artifact because content cannot have the same sha256 sum.</p>
<p>As such if you create content incorrectly, there is literally now way out of it.</p>