Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-07-28T11:43:11ZPulp
Planio Debian Support - Issue #9164 (CLOSED - CURRENTRELEASE): Dropping Python 3.6 and 3.7 from the 2.14...https://pulp.plan.io/issues/91642021-07-28T11:43:11Zquba42
<p>It looks like this was merged prematurely on my part.</p>
<p>Users have reported the following:</p>
<pre><code>I tried to update pulp_deb plugins using ansible but getting error as per below.
TASK [pulp.pulp_installer.pulp_common : Install prerequisites] ******************************************************************************************************************************************************************************
fatal: [pulptest008.karmalab.net]: FAILED! => {"changed": false, "msg": "No package matching 'rh-python38-python' found available, installed or updated", "rc": 126, "results": ["python-setuptools-0.9.8-7.el7.noarch providing python-setuptools is already installed", "No package matching 'rh-python38-python' found available, installed or updated"]}
</code></pre>
<p>Fresh installs are also suffering weird dependency effects where Python 3 is not being installed at all.</p> RPM Support - Story #9131 (CLOSED - DUPLICATE): As an administrator, I'd like RPM repository sync...https://pulp.plan.io/issues/91312021-07-23T06:13:18Zwibbit
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2286":<a href="https://github.com/pulp/pulp_rpm/issues/2286" class="external">https://github.com/pulp/pulp_rpm/issues/2286</a></p>
<hr>
<p>Currently, though Pulp3 supports mirror lists, it does not currently support re-trying against a different host in the mirror list in the event of a package sync failure.</p>
<p>While attempting to use mirror lists while syncing fedora34 updates, after ~15 attempts I was not able to get to version 1 of the repository, as each time it would try and it would get a new mirror, and there would be a failed package of some kind.</p>
<p>Anecdotally I see this a lot when running a dnf update/upgrade where packages will fail and DNF will happily go off and try a new mirror, without this logic, for larger repositories that may have a lot of change, I'm unsure of the value of supporting mirror lists.</p> Debian Support - Task #8682 (CLOSED - CURRENTRELEASE): Migrate to new Distribution model for pulp...https://pulp.plan.io/issues/86822021-05-03T12:21:35Zquba42Debian Support - Issue #8671 (CLOSED - CURRENTRELEASE): Sync with Main Debian Repo fails on a tra...https://pulp.plan.io/issues/86712021-04-30T08:43:16Ztp-hlawatsch
<p>Hello everybody,</p>
<p>we plan to use pulp as our main tool for repos . We testing at the moment Debian mirroring
Our pulp testinstance is runing with the latest offical docker image</p>
<p>This is the configured remote repo</p>
<p>{
"name": "debian",
"url": "<a href="http://ftp.de.debian.org/debian/" class="external">http://ftp.de.debian.org/debian/</a>",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": false,
"proxy_url": null,
"proxy_username": null,
"proxy_password": null,
"username": null,
"password": null,
"pulp_labels": {},
"download_concurrency": "10",
"policy": "immediate",
"total_timeout": null,
"connect_timeout": null,
"sock_connect_timeout": null,
"sock_read_timeout": null,
"rate_limit": null,
"distributions": "buster",
"components": "main",
"architectures": "amd64",
"sync_sources": false,
"sync_udebs": false,
"sync_installer": false,
"gpgkey": null,
"ignore_missing_package_indices": false
}</p>
<p>the sync run in to the following error</p>
<p>{
"pulp_href": "/pulp/api/v3/tasks/a7bd851b-f001-4f5f-89eb-0e0de529a556/",
"pulp_created": "2021-04-30T07:53:11.537345Z",
"state": "failed",
"name": "pulp_deb.app.tasks.synchronizing.synchronize",
"logging_cid": "00de2125667f4c7e8b8e01554c401eeb",
"started_at": "2021-04-30T07:53:11.648803Z",
"finished_at": "2021-04-30T07:53:19.135647Z",
"error": {
"traceback": " File "/usr/local/lib/python3.6/site-packages/rq/worker.py", line 1008, in perform_job\n rv = job.perform()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 706, in perform\n self._result = self._execute()\n File "/usr/local/lib/python3.6/site-packages/rq/job.py", line 729, in _execute\n result = self.func(*self.args, **self.kwargs)\n File "/usr/local/lib/python3.6/site-packages/pulp_deb/app/tasks/synchronizing.py", line 122, in synchronize\n DebDeclarativeVersion(first_stage, repository, mirror=mirror).create()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/declarative_version.py", line 149, in create\n loop.run_until_complete(pipeline)\n File "/usr/lib64/python3.6/asyncio/base_events.py", line 484, in run_until_complete\n return future.result()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 225, in create_pipeline\n await asyncio.gather(*futures)\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/api.py", line 43, in <strong>call</strong>\n await self.run()\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 266, in run\n RemoteArtifact.objects.bulk_get_or_create(self._needed_remote_artifacts(batch))\n File "/usr/local/lib/python3.6/site-packages/pulpcore/plugin/stages/artifact_stages.py", line 324, in _needed_remote_artifacts\n msg.format(rp=content_artifact.relative_path, c=d_content.content)\n",
"description": "No declared artifact with relative path "dists/buster/main/i18n/Translation-ml.bz2" for content """
},</p>
<p>We do not see a misconfiguration on our side so I raised this issue here</p>
<p>Regards
Stephan Hlawatsch</p> Debian Support - Task #8642 (CLOSED - DUPLICATE): Fix nightly testshttps://pulp.plan.io/issues/86422021-04-28T07:05:19Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/404":<a href="https://github.com/pulp/pulp_deb/issues/404" class="external">https://github.com/pulp/pulp_deb/issues/404</a></p>
<hr>
<p>Nightly tests have been consistently failing for a long time.</p>
<p>Nightly tests provide important information and should be fixed.</p> Debian Support - Task #8640 (CLOSED - DUPLICATE): Signature tests should provide proper SigningSe...https://pulp.plan.io/issues/86402021-04-28T06:59:31Zquba42
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_deb/402":<a href="https://github.com/pulp/pulp_deb/issues/402" class="external">https://github.com/pulp/pulp_deb/issues/402</a></p>
<hr>
<p>The setup of the SigningService for the test pipeline is currently a dirty hack, that causes frequent failures and complications in new pipelines.</p>
<p>It should be possible for the test itself to handle the setup using the pulpcore-manager utility functions provided by pulp-smash.</p> Debian Support - Task #8388 (CLOSED - CURRENTRELEASE): Handle ALLOWED_CONTENT_CHECKSUMS settinghttps://pulp.plan.io/issues/83882021-03-11T14:59:24Zquba42
<p>Right now the pulp_deb plugin is dependend on the following hashs being present on artifacts: md5, sha1, sha256, sha512.</p>
<p>Starting with pulpcore 3.11 will exclude md5 and sha1 from ALLOWED_CONTENT_CHECKSUMS by default.</p>
<p>Pulp deb will need to handle this gracefully. There is still some debate on whether pulp_deb makes sense without md5 feature wise. As a result, the solution may need to include demanding or encouraging a different configuration from pulp_deb users than the pulpcore default configuration.</p>
<p>See the following mailing list threads:</p>
<ul>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-February/msg00017.html</a></li>
<li><a href="https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html" class="external">https://listman.redhat.com/archives/pulp-dev/2021-March/msg00013.html</a></li>
</ul> CertGuard - Issue #7182 (CLOSED - CURRENTRELEASE): The docs aren't buildinghttps://pulp.plan.io/issues/71822020-07-21T20:25:23Zbmbouterbmbouter@redhat.com
<a name="The-docs-site-on-RTD-is-no-longer-building"></a>
<h2 >The docs site on RTD is no longer building<a href="#The-docs-site-on-RTD-is-no-longer-building" class="wiki-anchor">¶</a></h2>
<p>You can see the 1.0.0 and 1.0.1 changelogs are not present: <a href="https://pulp-certguard.readthedocs.io/en/latest/changes.html" class="external">https://pulp-certguard.readthedocs.io/en/latest/changes.html</a></p>
<p>The last successful build was Completed June 30, 2020. 6:54 p.m from (6d951eb3203a19f627d1f3e0e729f8c3a3107c0b)</p>
<p>The RTD builder fails with:</p>
<pre><code>DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting PyOpenSSL
Downloading pyOpenSSL-19.1.0-py2.py3-none-any.whl (53 kB)
ERROR: Could not find a version that satisfies the requirement pulpcore<3.6,>=3.3 (from -r requirements.txt (line 2)) (from versions: 3.0.0a1.dev3, 3.0.0a1.dev4, 3.0.0a1.dev5, 3.0.0a1, 3.0.0a2, 3.0.0a3, 3.0.0a4, 3.0.0a5, 3.0.0a6, 3.0.0a7, 3.0.0a8, 3.0.0a9, 3.0.0a10, 3.0.0a11, 3.0.0a12, 3.0.0a13, 3.0.0a14, 3.0.0a15, 3.0.0a16, 3.0.0a17, 3.0.0a18, 3.0.0a19, 3.0.0a20, 3.0.0a21, 3.0.0a22, 3.0.0a23, 3.0.0a24, 3.0.0a25, 3.0.0a26, 3.0.0a27, 3.0.0a28, 3.0.0a29, 3.0.0b1, 3.0.0b2, 3.0.0b3, 3.0.0b4, 3.0.0b5, 3.0.0b6, 3.0.0b7)
ERROR: No matching distribution found for pulpcore<3.6,>=3.3 (from -r requirements.txt (line 2))
</code></pre> CertGuard - Task #6830 (CLOSED - DUPLICATE): Update yum/dnf documentation on how .repo files can ...https://pulp.plan.io/issues/68302020-05-26T20:09:01Zbmbouterbmbouter@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp-certguard/142":<a href="https://github.com/pulp/pulp-certguard/issues/142" class="external">https://github.com/pulp/pulp-certguard/issues/142</a></p>
<hr>
<p>The cert and key from clients now occur during TLS submission. That means <a href="https://pulp-certguard.readthedocs.io/en/latest/yum-howto.html" class="external">these docs</a> are out of date.</p>
<p>We should update the docs to show how a yum/dnf client can be configured to submit the cert and key via TLS.</p> File Support - Test #5467 (CLOSED - DUPLICATE): Test - sync does not report non-fatal errors prop...https://pulp.plan.io/issues/54672019-09-17T19:41:05Zkersom
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_file/620":<a href="https://github.com/pulp/pulp_file/issues/620" class="external">https://github.com/pulp/pulp_file/issues/620</a></p>
<hr>
<p>If you sync a file repository where one of the files is missing, it seems that the repository syncs as much as it can (as expected), but its reported as a fatal error, with a state of 'failed'.</p>
<p>Steps to reproduce:</p>
<p>1) create a file repository where one of the files is missing<br>
2) create a file remote and repository and sync them</p>
<p>Actual task status (apologies its been yaml-fied):</p>
<pre><code>- _href: "/pulp/api/v3/tasks/b6f9b619-c174-4e43-b546-0bbefdfb11e7/"
_created: '2019-08-15T15:21:37.058+00:00'
state: failed
name: pulp_file.app.tasks.synchronizing.synchronize
started_at: '2019-08-15T15:21:37.177+00:00'
finished_at: '2019-08-15T15:21:37.382+00:00'
non_fatal_errors: "[]"
error:
code: ''
description: 404, message='Not Found'
traceback: |2
File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py", line 822, in perform_job
rv = job.perform()
File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 605, in perform
self._result = self._execute()
File "/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py", line 611, in _execute
return self.func(*self.args, **self.kwargs)
File "/usr/local/lib/pulp/src/pulp-file/pulp_file/app/tasks/synchronizing.py", line 45, in synchronize
dv.create()
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/declarative_version.py", line 169, 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 "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/api.py", line 209, in create_pipeline
await asyncio.gather(*futures)
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/api.py", line 43, in __call__
await self.run()
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/artifact_stages.py", line 132, in run
pb.done += task.result() # download_count
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/artifact_stages.py", line 155, in _handle_content_unit
await asyncio.gather(*downloaders_for_content)
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/stages/models.py", line 78, in download
download_result = await downloader.run(extra_data=self.extra_data)
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/download/base.py", line 212, in run
return await self._run(extra_data=extra_data)
File "/usr/local/lib/pulp/lib64/python3.6/site-packages/backoff/_async.py", line 131, in retry
ret = await target(*args, **kwargs)
File "/usr/local/lib/pulp/src/pulpcore-plugin/pulpcore/plugin/download/http.py", line 183, in _run
response.raise_for_status()
File "/usr/local/lib/pulp/lib64/python3.6/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
headers=self.headers)
worker: "/pulp/api/v3/workers/df7e0085-b0dd-4073-b74d-9ab78ad27a03/"
spawned_tasks: []
progress_reports:
- message: Downloading Metadata
state: completed
total: 1
done: 1
- message: Parsing Metadata Lines
state: completed
total: 2
done: 2
- message: Downloading Artifacts
state: failed
done: 0
- message: Associating Content
state: canceled
done: 0
created_resources: []
reserved_resources_record: []
create_version: true
poll_attempts:
total: 1
failed: 1
</code></pre>
<p>I'd expect this error to be in the 'non-fatal' errors attribute, and the state to not be 'failed'</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 #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 #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> File Support - Test #5036 (CLOSED - DUPLICATE): Test that syncing protected content workshttps://pulp.plan.io/issues/50362019-06-25T22:15:41Zdkliban@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_file/614":<a href="https://github.com/pulp/pulp_file/issues/614" class="external">https://github.com/pulp/pulp_file/issues/614</a></p>
<hr>
<p>File Remote supports syncing from protected repositories. Users must provide an 'ssl_client_key' and 'ssl_client_certificate' when creating a File Remote[0].</p>
<p>The following should cover this use case.</p>
<p>1) Create repository<br>
2) Create a repository version with some content<br>
3) Create a publication<br>
4) Create a content guard<br>
5) Create distribution that is associated with the publication and the content guard.<br>
6) Create another repository<br>
7) Create a remote that has a URL pointing at the Distribution from step 5 and uses the client certificate for the content guard<br>
8) Create a repository version for the second repository by syncing from the remote<br>
9) Assert that the sync is successful<br>
10) Update the remote with a different client certificate<br>
11) Sync from the remote again<br>
12) Assert a failure occurs.</p>
<p>[0] <a href="https://docs.pulpproject.org/en/3.0/nightly/restapi.html#operation/remotes_file_file_create" class="external">https://docs.pulpproject.org/en/3.0/nightly/restapi.html#operation/remotes_file_file_create</a></p> Pulp - Story #3778 (CLOSED - CURRENTRELEASE): [Epic] As a user, I can run Pulp 3 in a FIPS-enable...https://pulp.plan.io/issues/37782018-06-21T16:13:49Zdaviddavis