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 #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> RPM Support - Issue #8944 (CLOSED - CURRENTRELEASE): Cannot sync RHEL6 repos from cdn.redhat.comhttps://pulp.plan.io/issues/89442021-06-21T22:37:08Zsskracic@redhat.comsskracic@redhat.com
<ul>
<li>a containerized pulp based on pulp-ci-centos image with:</li>
</ul>
<p>pulpcore-3.13.0
pulp-rpm-3.13.0</p>
<p>I am not sure whether it's a Pulp bug or a CDN data error, but RHEL6 i386 and x86_64
repo syncing repeatedly fails with this error. The repositories are synced with mirror=True
and the distribution is set to point to repository (so that the latest repo is always distributed).</p>
<pre><code>Repo: Red Hat Enterprise Linux 6 Server from RHUI (RPMs) (6Server-i386)
Start Time: 2021-06-21 22:24:04
Finish Time: 2021-06-21 22:28:18
Elapsed Time: 0:04:13.581718
Result: Error
Exception: Package id from primary metadata (42003b3621ebf25f9b5fe25b0d2c4f2024958a9d), does not match package id from filelists, other metadata (dcacfd1c930cba9ee112c1055e7a1e94bedd7f3a)
Traceback: File "/usr/local/lib/python3.6/site-packages/rq/worker.py", line 1013, in perform_job
rv job.perform()
File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 709, in perform
self._result = self._execute()
File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 732, in _execute
result = self.func(*self.args, **self.kwargs)
File "/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 395, in synchronize
version = dv.create()
File "/src/pulpcore/pulpcore/plugin/stages/declarative_version.py", line 149, in create
loop.run_until_complete(pipeline)
File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete
return future.result()
File "/src/pulpcore/pulpcore/plugin/stages/api.py", line 225, in create_pipeline
await asyncio.gather(*futures)
File "/src/pulpcore/pulpcore/plugin/stages/api.py", line 43, in __call__
await self.run()
File "/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 674, in run
await self.parse_repository_metadata(repomd, repomd_files, file_extension)
File "/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 719, in parse_repository_metadata
file_extension=file_extension,
File "/src/pulp-rpm/pulp_rpm/app/tasks/synchronizing.py", line 987, in parse_packages
).format(pkgid, pkgid_extra)
</code></pre> 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 #7867 (CLOSED - WONTFIX): Issue #7796 : Pulp Version 2.20 - Mongod and pulp_celerybe...https://pulp.plan.io/issues/78672020-11-19T11:53:20Ztosif.meman@kindredgroup.com
<p>Hello Team,</p>
<p>We have pulp version 2.20 configured in our environment and we have faced challenges as mongodb randomly stopped working and due to that pulp_celerybeat not able to connect to the database and apparently the result is pulp_celerybeat also failing.</p>
<p>mongodb version - mongodb-org-server-3.2.22-1.el7.x86_64</p>
<p>The logs did not helped me either as logs not showing sufficient info to troubleshoot.</p>
<p>localhost: pulp: kombu.async.hub:ERROR: (23150-55872) File "/usr/lib/python2.7/site-packages/pulp/server/async/app.py", line 119, in _record_heartbeat pulp: kombu.async.hub:ERROR: (23141-69152) File "/usr/lib/python2.7/site-packages/pulp/server/async/worker_watcher.py", line 39, in handle_worker_heartbeat pulp: kombu.async.hub:ERROR: (23240-19648) File "/usr/lib/python2.7/site-packages/pulp/server/async/worker_watcher.py", line 39, in handle_worker_heartbeat</p>
<p>MongoDB logs:</p>
<p>2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] db version v3.2.22
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] git version: 105acca0d443f9a47c1a5bd608fd7133840a58dd
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] allocator: tcmalloc
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] modules: none
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] build environment:
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] distmod: rhel70
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] distarch: x86_64
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] target_arch: x86_64
2020-11-04T12:19:29.375+0100 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1" }, processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid" }, security: { authorization: "disabled" }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongodb.log" } }
2020-11-04T12:19:29.404+0100 I - [initandlisten] Detected data files in /var/lib/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2020-11-04T12:19:29.404+0100 W - [initandlisten] Detected unclean shutdown - /var/lib/mongodb/mongod.lock is not empty.
2020-11-04T12:19:29.404+0100 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2020-11-04T12:19:29.404+0100 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=18G,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),</p>
<p>2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten]
2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten] ** We suggest setting it to 'never'
2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten]
2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2020-11-04T12:19:30.164+0100 I CONTROL [initandlisten] ** We suggest setting it to 'never'
2020-11-04T12:19:30.165+0100 I CONTROL [initandlisten]
2020-11-04T12:19:30.165+0100 I CONTROL [initandlisten] ** WARNING: soft rlimits too low. rlimits set to 4096 processes, 64000 files. Number of processes should be at least 32000 : 0.5 times number of files.</p> RPM Support - Issue #7786 (CLOSED - WORKSFORME): Pulp_rpm sync reports "completed" but does not u...https://pulp.plan.io/issues/77862020-11-04T07:51:35ZAant
<p>This is a copy of <a href="https://pulp.plan.io/issues/7535?next_issue_id=7534" class="external">https://pulp.plan.io/issues/7535?next_issue_id=7534</a>. The issue persists.
Even if I delete and recreate the publication and distribution after synchronization I still experience this issue.
This is a very severe bug as it makes me believe that my systems are up to date while they are not.</p>
<a name="What-would-be-the-proper-workflow-to-resynchronise-a-repo-after-it-is-created"></a>
<h2 >What would be the proper workflow to resynchronise a repo after it is created?<a href="#What-would-be-the-proper-workflow-to-resynchronise-a-repo-after-it-is-created" class="wiki-anchor">¶</a></h2>
<p>I have set up Pulpcore v3.6.3 with Pulp_rpm v3.6.2 - later updated both to 3.7.0.
I created the following remote:</p>
<pre><code>{
"pulp_href": "/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/",
"pulp_created": "2020-08-18T08:47:19.183836Z",
"name": "centos8_base",
"url": "http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": true,
"proxy_url": "http://<proxy server>",
"username": null,
"password": null,
"pulp_last_updated": "2020-08-18T08:47:19.183855Z",
"download_concurrency": 10,
"policy": "immediate",
"sles_auth_token": null
}
</code></pre>
<p>and this repository:</p>
<pre><code>{
"pulp_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/",
"pulp_created": "2020-08-18T08:47:17.704104Z",
"versions_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/versions/",
"latest_version_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/versions/1/",
"name": "centos8_base",
"description": null,
"remote": null,
"metadata_signing_service": null,
"retain_package_versions": 0
}
</code></pre>
<p>If I sync, it reports success:</p>
<pre><code>http --auth admin --auth-type basic :9000/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/sync/ remote=/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/
http: password for admin@localhost:9000:
HTTP/1.1 202 Accepted
Allow: POST, OPTIONS
Connection: close
Content-Length: 67
Content-Type: application/json
Date: Mon, 21 Sep 2020 08:10:11 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN
{
"task": "/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/"
}
</code></pre>
<p>Let's take a closer look at the task:</p>
<pre><code> http --auth admin --auth-type basic :9000/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/
http: password for admin@localhost:9000:
HTTP/1.1 200 OK
Allow: GET, PATCH, DELETE, HEAD, OPTIONS
Connection: close
Content-Length: 743
Content-Type: application/json
Date: Mon, 21 Sep 2020 08:10:29 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN
{
"child_tasks": [],
"created_resources": [],
"error": null,
"finished_at": "2020-09-21T08:10:11.585792Z",
"name": "pulp_rpm.app.tasks.synchronizing.synchronize",
"parent_task": null,
"progress_reports": [
{
"code": "optimizing.sync",
"done": 1,
"message": "Optimizing Sync",
"state": "completed",
"suffix": null,
"total": null
}
],
"pulp_created": "2020-09-21T08:10:11.257796Z",
"pulp_href": "/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/",
"reserved_resources_record": [
"/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/",
"/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/"
],
"started_at": "2020-09-21T08:10:11.507912Z",
"state": "completed",
"task_group": null,
"worker": "/pulp/api/v3/workers/80ca382e-fdec-4eef-94b4-6c1c67433511/"
}
</code></pre>
<p>Let's use this repo on the same machine:</p>
<pre><code>cat /etc/yum.repos.d/CentOS-Base.repo
[Base]
name=CentOS-$releasever - Base
enabled=1
baseurl=https://<myurl>/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
</code></pre>
<p>Now if I do <code>yum check-update</code> it does not find any package to update.
If I change <code>baseurl=</code> to <code>http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/</code> (which is the same url I have in the remote) and I do <code>yum check-update</code>, then it finds 28 outdated packages. How is it possible?</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 #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> RPM Support - Issue #7535 (CLOSED - WORKSFORME): Pulp_rpm sync reports "completed" but does not u...https://pulp.plan.io/issues/75352020-09-21T08:28:31ZAant
<p>I have set up Pulpcore v3.6.3 with Pulp_rpm v3.6.2.
I created the following remote:</p>
<pre><code>{
"pulp_href": "/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/",
"pulp_created": "2020-08-18T08:47:19.183836Z",
"name": "centos8_base",
"url": "http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": true,
"proxy_url": "http://<proxy server>",
"username": null,
"password": null,
"pulp_last_updated": "2020-08-18T08:47:19.183855Z",
"download_concurrency": 10,
"policy": "immediate",
"sles_auth_token": null
}
</code></pre>
<p>and this repository:</p>
<pre><code>{
"pulp_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/",
"pulp_created": "2020-08-18T08:47:17.704104Z",
"versions_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/versions/",
"latest_version_href": "/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/versions/1/",
"name": "centos8_base",
"description": null,
"remote": null,
"metadata_signing_service": null,
"retain_package_versions": 0
}
</code></pre>
<p>If I sync, it reports success:</p>
<pre><code>http --auth admin --auth-type basic :9000/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/sync/ remote=/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/
http: password for admin@localhost:9000:
HTTP/1.1 202 Accepted
Allow: POST, OPTIONS
Connection: close
Content-Length: 67
Content-Type: application/json
Date: Mon, 21 Sep 2020 08:10:11 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN
{
"task": "/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/"
}
</code></pre>
<p>Let's take a closer look at the task:</p>
<pre><code> http --auth admin --auth-type basic :9000/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/
http: password for admin@localhost:9000:
HTTP/1.1 200 OK
Allow: GET, PATCH, DELETE, HEAD, OPTIONS
Connection: close
Content-Length: 743
Content-Type: application/json
Date: Mon, 21 Sep 2020 08:10:29 GMT
Server: gunicorn/20.0.4
Vary: Accept, Cookie
X-Frame-Options: SAMEORIGIN
{
"child_tasks": [],
"created_resources": [],
"error": null,
"finished_at": "2020-09-21T08:10:11.585792Z",
"name": "pulp_rpm.app.tasks.synchronizing.synchronize",
"parent_task": null,
"progress_reports": [
{
"code": "optimizing.sync",
"done": 1,
"message": "Optimizing Sync",
"state": "completed",
"suffix": null,
"total": null
}
],
"pulp_created": "2020-09-21T08:10:11.257796Z",
"pulp_href": "/pulp/api/v3/tasks/655d2e7b-2783-4496-a851-3bcd8d5e442e/",
"reserved_resources_record": [
"/pulp/api/v3/remotes/rpm/rpm/d8fb524c-e73b-4afc-ba2e-05eea7f5b6a8/",
"/pulp/api/v3/repositories/rpm/rpm/7696b222-3788-4754-b4a6-747e64228d7a/"
],
"started_at": "2020-09-21T08:10:11.507912Z",
"state": "completed",
"task_group": null,
"worker": "/pulp/api/v3/workers/80ca382e-fdec-4eef-94b4-6c1c67433511/"
}
</code></pre>
<p>Let's use this repo on the same machine:</p>
<pre><code>cat /etc/yum.repos.d/CentOS-Base.repo
[Base]
name=CentOS-$releasever - Base
enabled=1
baseurl=https://<myurl>/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-centosofficial
</code></pre>
<p>Now if I do <code>yum check-update</code> it does not find any package to update.
If I change <code>baseurl=</code> to <code>http://mirror.centos.org/centos-8/8/BaseOS/x86_64/os/</code> (which is the same url I have in the remote) and I do <code>yum check-update</code>, then it finds 28 outdated packages. How is it possible?</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> Debian Support - Issue #6873 (CLOSED - DUPLICATE): Pulp 3 - pulp-deb : APT client notb working du...https://pulp.plan.io/issues/68732020-06-01T19:09:23Zswisscom
<p>Dear support team,</p>
<p>The paths in Release files created by Pulp (pulp-deb plugin) wre wrong. It contain full path (dists/)/...
instead of "...." only.</p>
<p>Example from <a href="http://ftp.debian.org/debian/dists/buster/Release" class="external">http://ftp.debian.org/debian/dists/buster/Release</a> :</p>
<pre><code class="python syntaxhl" data-language="python"><span class="n">MD5Sum</span><span class="p">:</span>
<span class="mi">11</span><span class="n">bc5601662d8b6f5b24a92d28150fee</span> <span class="mi">1363066</span> <span class="n">contrib</span><span class="o">/</span><span class="n">Contents</span><span class="o">-</span><span class="n">amd64</span>
<span class="mi">3059916</span><span class="n">a1fef8d912df26e4e537c87f0</span> <span class="mi">103346</span> <span class="n">contrib</span><span class="o">/</span><span class="n">Contents</span><span class="o">-</span><span class="n">amd64</span><span class="p">.</span><span class="n">gz</span>
<span class="n">ccfc6bac526797636a618f18cdce393c</span> <span class="mi">1081641</span> <span class="n">contrib</span><span class="o">/</span><span class="n">Contents</span><span class="o">-</span><span class="n">arm64</span>
<span class="n">e4e018e33daf3f4f24732834af309669</span> <span class="mi">84796</span> <span class="n">contrib</span><span class="o">/</span><span class="n">Contents</span><span class="o">-</span><span class="n">arm64</span><span class="p">.</span><span class="n">gz</span>
</code></pre>
<p>Example from repo coming from Pulp :</p>
<pre><code class="python syntaxhl" data-language="python"><span class="n">Codename</span><span class="p">:</span> <span class="n">buster</span>
<span class="n">Date</span><span class="p">:</span> <span class="n">Sat</span><span class="p">,</span> <span class="mi">09</span> <span class="n">May</span> <span class="mi">2020</span> <span class="mi">09</span><span class="p">:</span><span class="mi">51</span><span class="p">:</span><span class="mi">02</span> <span class="n">UTC</span>
<span class="n">Architectures</span><span class="p">:</span> <span class="n">s390x</span> <span class="n">ppc64el</span> <span class="n">mipsel</span> <span class="n">mips64el</span> <span class="n">mips</span> <span class="n">i386</span> <span class="n">armhf</span> <span class="n">armel</span> <span class="n">arm64</span> <span class="n">amd64</span>
<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>
</code></pre>
<p>"dist/buster/" should not appear here as the path here must be relative from the place where the Release file is, to work prpoerly with the apt client.</p> RPM Support - Issue #6861 (CLOSED - CURRENTRELEASE): Migration from 3.2.0 to 3.3.z is brokenhttps://pulp.plan.io/issues/68612020-05-29T16:37:58Zdalleydalley@redhat.com
<p>In trying to resolve the migration issues between 3.3.0 and 3.3.1, we accidentally introduced a new blocking issue between 3.2.0 and 3.3.z.</p>
<p>Both migration 0005 and 0009 need to be modified, again, such that they both specify that 'last_sync_revision_number' is nullable.</p> Debian Support - Issue #6593 (CLOSED - NOTABUG): No plugin found: deb_distributorhttps://pulp.plan.io/issues/65932020-04-28T20:12:14Zymadav
<p>I have pulp 2.18 running on RHEL 7.7 and have all pulp debain packages and pulgin packages installed,I was able to create the repo but when i try to run the sync command it says like no plugin found or missing resources, during the delete of the repo also it is the same situation.Below are the my pulp packages.Can some one help me here.</p>
<p>python-pulp-rpm-common-2.18.1-1.el7.noarch
pulp-docker-admin-extensions-3.2.2-1.el7.noarch
pulp-deb-admin-extensions-1.8.0-1.el7.noarch
python-pulp-client-lib-2.18.1-2.el7.noarch
pulp-puppet-plugins-2.18.1-1.el7.noarch
python-pulp-docker-common-3.2.2-1.el7.noarch
pulp-server-2.18.1-2.el7.noarch
python-pulp-repoauth-2.18.1-2.el7.noarch
pulp-rpm-admin-extensions-2.18.1-1.el7.noarch
python-pulp-bindings-2.18.1-2.el7.noarch
pulp-rpm-plugins-2.18.1-1.el7.noarch
python-pulp-deb-common-1.8.0-1.el7.noarch
python-pulp-puppet-common-2.18.1-1.el7.noarch
pulp-selinux-2.18.1-2.el7.noarch
pulp-puppet-admin-extensions-2.18.1-1.el7.noarch
python-pulp-common-2.18.1-2.el7.noarch
pulp-admin-client-2.18.1-2.el7.noarch
pulp-docker-plugins-3.2.2-1.el7.noarch
python-pulp-oid_validation-2.18.1-2.el7.noarch
pulp-deb-plugins-1.8.0-1.el7.noarch</p>
<p>Erros i am getting are as like below.</p>
<p>pulp-admin deb repo publish run --repo-id xenial-backports-amd64
+----------------------------------------------------------------------+
Publishing Repository [xenial-backports-amd64]
+----------------------------------------------------------------------+</p>
<p>This command may be exited via ctrl+c without affecting the request.</p>
<p>Task Failed</p>
<p>No plugin found: deb_distributor</p>
<p>pulp-admin deb repo delete --repo-id xenial-newrelic-test
This command may be exited via ctrl+c without affecting the request.
[]
Running...
Task Failed
Pulp exception occurred: PulpExecutionException
No plugin found: deb_importer
No plugin found: deb_distributor</p>