Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2022-01-07T14:05:14ZPulp
Planio Pulp - Issue #9665 (CLOSED - DUPLICATE): Make the `adjust_roles` function accessible via plugin apihttps://pulp.plan.io/issues/96652022-01-07T14:05:14Zbmclaugh
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2092":<a href="https://github.com/pulp/pulpcore/issues/2092" class="external">https://github.com/pulp/pulpcore/issues/2092</a></p>
<hr>
<p>While migrating to the Roles backend I find I need to access <code>adjust_roles</code> [1] and CI throws an error when accessing it via <code>from pulpcore.app.apps import adjust_roles</code> [2].</p>
<p>[1] <a href="https://github.com/pulp/pulpcore/blob/main/pulpcore/app/apps.py#L269" class="external">https://github.com/pulp/pulpcore/blob/main/pulpcore/app/apps.py#L269</a>
[2] <a href="https://github.com/ansible/galaxy_ng/runs/4731797454?check_suite_focus=true" class="external">https://github.com/ansible/galaxy_ng/runs/4731797454?check_suite_focus=true</a></p> Pulp - Issue #9637 (CLOSED - DUPLICATE): has_remote_param_obj_perms assumes that pulpcore seriali...https://pulp.plan.io/issues/96372021-12-14T18:48:55Zttereshcttereshc@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2088":<a href="https://github.com/pulp/pulpcore/issues/2088" class="external">https://github.com/pulp/pulpcore/issues/2088</a></p>
<hr>
<p><a href="https://github.com/pulp/pulpcore/blob/e785f56d72469a7f602db6d2d347a2912e7cbf2e/pulpcore/app/global_access_conditions.py#L146" class="external">RepositorySyncURLSerializer is always used</a> in <code>has_remote_*_perms</code>.</p>
<p>It works only for plugins which do not have this serializer subclassed.</p>
<p>The error one may see is:</p>
<pre><code>E pulpcore.client.pulp_container.exceptions.ApiException: (400)
E Reason: Bad Request
E HTTP response headers: HTTPHeaderDict({'Server': 'nginx/1.14.1', 'Date': 'Mon, 13 Dec 2021 20:29:20 GMT', 'Content-Type': 'application/json', 'Content-Length': '36', 'Connection': 'keep-alive', 'Vary': 'Accept, Cookie', 'Allow': 'POST, OPTIONS', 'X-Frame-Options': 'DENY', 'X-Content-Type-Options': 'nosniff', 'Referrer-Policy': 'same-origin', 'Correlation-ID': 'b1b5beab65cd4d7d8923b5c2304b7338', 'Access-Control-Expose-Headers': 'Correlation-ID'})
E HTTP response body: {"your_plugin_specific_field_for_sync":["Unexpected field"]}
</code></pre>
<p>Everything works fine with an admin user, this error is seen only with non-admin users.</p>
<p>Pulp needs to use a serializer configured for the view[set].</p> RPM Support - Issue #9636 (CLOSED - DUPLICATE): FileNotFoundError: [Errno 2] No such file or dire...https://pulp.plan.io/issues/96362021-12-13T17:05:32Zttereshcttereshc@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2321":<a href="https://github.com/pulp/pulp_rpm/issues/2321" class="external">https://github.com/pulp/pulp_rpm/issues/2321</a></p>
<hr>
<p>Pulp expects custom metadata files to have a specific format for filenames: -.</p>
<p>During pulp-2to3-migration, users get <code>FileNotFoundError: [Errno 2] No such file or directory: ' '</code> because the filename is only a checksum :/, which we remove to determine the filename, so the path we detect becomes an empty string.</p>
<pre><code>Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: File "/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/migration.py", line 478, in migrate_repo_distributor
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: pulp2dist, repo_version)
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: File "/usr/lib/python3.6/site-packages/pulp_2to3_migration/app/plugin/rpm/repository.py", line 91, in migrate_to_pulp3
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: publish(repo_version.pk, checksum_types=checksum_types, sqlite_metadata=sqlite)
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: File "/usr/lib/python3.6/site-packages/pulp_rpm/app/tasks/publishing.py", line 344, in publish
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: publication_data.populate()
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: File "/usr/lib/python3.6/site-packages/pulp_rpm/app/tasks/publishing.py", line 253, in populate
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: self.repomdrecords = self.prepare_metadata_files(main_content)
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: File "/usr/lib/python3.6/site-packages/pulp_rpm/app/tasks/publishing.py", line 99, in prepare_metadata_files
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: with open(path, "wb") as new_file:
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: FileNotFoundError: [Errno 2] No such file or directory: ''
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-1: pulp: rq.worker:INFO: 27738@1002a1103081001.xxx.com: c0d58c5a-9ff1-4d40-bbb3-9c24fdf0fdb4
Nov 22 21:31:34 1002a1103081001 pulpcore-resource-manager: pulp: rq.worker:INFO: resource-manager: 43f43c1a-d09e-46bd-99fe-73b6e2ee397c
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-3: pulp: rq.worker:INFO: 27740@1002a1103081001.xxx.com: Job OK (b25f3fa2-401c-425c-92eb-b49a61415617)
Nov 22 21:31:34 1002a1103081001 pulpcore-worker-2: pulp: pulp_rpm.app.tasks.publishing:INFO: Publishing: repository=XXX-Red_Hat_Ansible_Engine_2_7_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64, version=1
</code></pre>
<p>Some repositories like <a href="https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhv-mgmt-agent/4/os/repodata/repomd.xml" class="external">https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhv-mgmt-agent/4/os/repodata/repomd.xml</a> have filenames in the form of UUID.</p>
<p>Observed with pulp2 to pulp3 migration only so far, need to test sync.</p> Pulp - Issue #9634 (CLOSED - DUPLICATE): Uploading large files fails on the "Too many open files"...https://pulp.plan.io/issues/96342021-12-13T14:37:33Zlmjachky
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulpcore/2087":<a href="https://github.com/pulp/pulpcore/issues/2087" class="external">https://github.com/pulp/pulpcore/issues/2087</a></p>
<hr>
<p>Steps to reproduce the behaviour:</p>
<pre><code>(pulp) [vagrant@pulp3-source-fedora34 pulp_ostree]$ truncate -s 3G gentoo_root.img
(pulp) [vagrant@pulp3-source-fedora34 pulp_ostree]$ pulp artifact upload --file gentoo_root.img
Uploading file gentoo_root.img
................[truncated the number of dots]...................Upload complete. Creating artifact.
Started background task /pulp/api/v3/tasks/2d3cf569-2d5c-449d-9ac6-7a53ab5f3a30/
........Error: Task /pulp/api/v3/tasks/2d3cf569-2d5c-449d-9ac6-7a53ab5f3a30/ failed: '[Errno 24] Too many open files: '/var/lib/pulp/media/upload/ec2d5c92-57e9-4191-ae95-ff4b9ec94353''
(pulp) [vagrant@pulp3-source-fedora34 pulp_ostree]$ ls -la gentoo_root.img
-rw-r--r--. 1 vagrant vagrant 3221225472 Dec 13 11:32 gentoo_root.img
</code></pre>
<p>Traceback:</p>
<pre><code>Task 2d3cf569-2d5c-449d-9ac6-7a53ab5f3a30 failed ([Errno 24] Too many open files: '/var/lib/pulp/media/upload/ec2d5c92-57e9-4191-ae95-ff4b9ec94353')
pulp [3a3a9ea662994f609eea7d43ac8f30aa]: pulpcore.tasking.pulpcore_worker:INFO: File "/home/vagrant/devel/pulpcore/pulpcore/tasking/pulpcore_worker.py", line 362, in _perform_task
result = func(*args, **kwargs)
File "/home/vagrant/devel/pulpcore/pulpcore/app/tasks/upload.py", line 31, in commit
temp_file.write(chunk.file.read())
File "/usr/local/lib/pulp/lib64/python3.9/site-packages/django/core/files/utils.py", line 42, in <lambda>
read = property(lambda self: self.file.read)
File "/usr/local/lib/pulp/lib64/python3.9/site-packages/django/db/models/fields/files.py", line 45, in _get_file
self._file = self.storage.open(self.name, 'rb')
File "/usr/local/lib/pulp/lib64/python3.9/site-packages/django/core/files/storage.py", line 38, in open
return self._open(name, mode)
File "/usr/local/lib/pulp/lib64/python3.9/site-packages/django/core/files/storage.py", line 238, in _open
return File(open(self.path(name), mode))
</code></pre> RPM Support - Test #9626 (CLOSED - DUPLICATE): Add tests for SHA repo to test_synchttps://pulp.plan.io/issues/96262021-12-08T21:43:04Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2320":<a href="https://github.com/pulp/pulp_rpm/issues/2320" class="external">https://github.com/pulp/pulp_rpm/issues/2320</a></p>
<hr>
<p>We have been bitten a few times now by repos that use 'sha' (instead of 'sha1') checksums. Build a test for same that does <strong>not</strong> require sync'ing all of RHEL6.6...</p> RPM Support - Issue #9583 (CLOSED - DUPLICATE): Distribution tree uniqueness constraint is not en...https://pulp.plan.io/issues/95832021-11-23T17:43:48Zttereshcttereshc@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2305":<a href="https://github.com/pulp/pulp_rpm/issues/2305" class="external">https://github.com/pulp/pulp_rpm/issues/2305</a></p>
<hr>
<p>Currently <a href="https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/models/distribution.py#L133" class="external">Pulp requires</a> the combination of the following fields to be unique:</p>
<pre><code> unique_together = (
"header_version",
"release_name",
"release_short",
"release_version",
"arch",
"build_timestamp",
)
</code></pre>
<p>In some cases, it doesn't seem enough.
For some reason multiple repositories might have all those fields exactly the same and they differ in variants definition only. Such are not proper distribution trees, the majority do not have any images associated.</p>
<p>Examples brought by always helpful @gdve from <a href="https://pulp.plan.io/issues/8566#note-33" class="external">https://pulp.plan.io/issues/8566#note-33</a>:</p>
<pre><code>CentOS/8-stream/AppStream/x86_64/os/.treeinfo:build_timestamp = 1625615144
CentOS/8-stream/BaseOS/x86_64/os/.treeinfo:build_timestamp = 1625615155
CentOS/8-stream/HighAvailability/x86_64/os/.treeinfo:build_timestamp = 1625026406
CentOS/8-stream/PowerTools/x86_64/os/.treeinfo:build_timestamp = 1625026406
CentOS/8-stream/RT/x86_64/os/.treeinfo:build_timestamp = 1625026406
</code></pre>
<pre><code>AlmaLinux/8.4/AppStream/x86_64/kickstart/.treeinfo:build_timestamp = 1622014553
AlmaLinux/8.4/AppStream/x86_64/os/.treeinfo:build_timestamp = 1622014553
AlmaLinux/8.4/BaseOS/x86_64/kickstart/.treeinfo:build_timestamp = 1622014553
AlmaLinux/8.4/BaseOS/x86_64/os/.treeinfo:build_timestamp = 1622014553
AlmaLinux/8.4/HighAvailability/x86_64/kickstart/.treeinfo:build_timestamp = 1622014558
AlmaLinux/8.4/HighAvailability/x86_64/os/.treeinfo:build_timestamp = 1622014558
AlmaLinux/8.4/PowerTools/x86_64/kickstart/.treeinfo:build_timestamp = 1622014558
AlmaLinux/8.4/PowerTools/x86_64/os/.treeinfo:build_timestamp = 1622014558
AlmaLinux/8.4/extras/x86_64/kickstart/.treeinfo:build_timestamp = 1622014558
AlmaLinux/8.4/extras/x86_64/os/.treeinfo:build_timestamp = 1622014558
</code></pre>
<p>Pulp 2to3 migration fails with <code>No declared artifact with relative path ".treeinfo" for content "<DistributionTree: pk=64f44866-0207-4005-9c06-0f45e52cbdd1>"</code>.
I would expect sync to behave the similarly, needs testing though.</p> Pulp - Task #9575 (CLOSED - WONTFIX): Move queryset filtering for Tasks to Task.objectshttps://pulp.plan.io/issues/95752021-11-18T21:06:16Zbmbouterbmbouter@redhat.com
<p>Right now the Task queryset scoping is implemented only in DRF. Recently the new task purge endpoint deletes task records in a task. To do that in a way that aligns with the queryset scoping and RBAC the Tasks endpoint already supports we have to have the queryset manager provide the queryset scoping.</p> RPM Support - Issue #9566 (CLOSED - DUPLICATE): Create better primary keys for subtreeshttps://pulp.plan.io/issues/95662021-11-12T13:21:31Zholger.hees
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2304":<a href="https://github.com/pulp/pulp_rpm/issues/2304" class="external">https://github.com/pulp/pulp_rpm/issues/2304</a></p>
<hr>
<p>Scenario:</p>
<p>My primary pulp instance is hosting 2 distributions of the same repository (like staging and production) which are referencing different versions of the same repository. During my initial run, both distributions are point to version 1. So far so good.</p>
<p>Now I have a secondary pulp instance which is mirroring the 2 primary distributions by creating separate remotes and repositories.</p>
<p>The repository on the primary node contains now a subtree which is identically in version 1 for staging and production. Means it has the same hash.</p>
<p>Now, during the sync process the metadata for this subtree are stored by createing a primary key like "{repodata}-{treeinfo['hash']}". This collides with staging and production, because contentwise and with the hash, the subtree is the same for both staging and production. The key should be something like "{repodata}-{treeinfo['hash']}-{repository_pk}"</p>
<p><a href="https://github.com/pulp/pulp_rpm/pull/2173" class="external">https://github.com/pulp/pulp_rpm/pull/2173</a></p> Container Support - Story #9509 (CLOSED - DUPLICATE): As a user I can sign container image by pro...https://pulp.plan.io/issues/95092021-10-14T10:14:23Zipanova@redhat.comipanova@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/500":<a href="https://github.com/pulp/pulp_container/issues/500" class="external">https://github.com/pulp/pulp_container/issues/500</a></p>
<hr>
<p>As a result signature will be created and saved into the Pulp Container Registry Sigstore</p>
<p>It should be possible to sign whole repo, list of images or a specific image only.</p>
<p>See <a href="https://github.com/containers/skopeo/blob/main/docs/skopeo-standalone-sign.1.md" class="external">https://github.com/containers/skopeo/blob/main/docs/skopeo-standalone-sign.1.md</a> and <a href="https://github.com/containers/image/blob/main/docs/containers-signature.5.md#json-data-format" class="external">https://github.com/containers/image/blob/main/docs/containers-signature.5.md#json-data-format</a></p> Container Support - Story #9507 (CLOSED - DUPLICATE): As a user I can sync container image with i...https://pulp.plan.io/issues/95072021-10-14T10:12:04Zipanova@redhat.comipanova@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/498":<a href="https://github.com/pulp/pulp_container/issues/498" class="external">https://github.com/pulp/pulp_container/issues/498</a></p>
<hr>
<p>Synced signatures are not verified. Signature verification is offloaded to the client.</p>
<p>If <code>with-signature=True</code> ( TBD agree on naming) was specified only those images that have signature with be mirrored. Rest of the images will be skipped. <code>Signature server location</code> needs to be specified ( it's the webserver location of signatures, for example <a href="https://registry.redhat.io/containers/sigstore" class="external">https://registry.redhat.io/containers/sigstore</a>).
Otherwise it will be assumed that the signature is stored on the remote registry in a form of manifest or a separate object:</p>
<ul>
<li>If it is a separate object, signature API extensions should be available on the registry and <code>X-Registry-Supports-Signatures</code> header will identify that <a href="https://github.com/containers/image/blob/main/docs/signature-protocols.md#openshift-dockerdistribution-api-extension" class="external">https://github.com/containers/image/blob/main/docs/signature-protocols.md#openshift-dockerdistribution-api-extension</a>
</li>
<li>If it is stored in a form of a manifest then it most likely was signed with cosign <a href="https://github.com/SigStore/cosign#signing-subjects" class="external">https://github.com/SigStore/cosign#signing-subjects</a>. <strong>we will not support this for now</strong>
</li>
</ul>
<p><strong>Q:</strong> does podman/skopeo support verification of cosign signature type? Only atomic type for now <a href="https://github.com/containers/image/blob/main/docs/containers-signature.5.md#criticaltype" class="external">https://github.com/containers/image/blob/main/docs/containers-signature.5.md#criticaltype</a></p>
<p><strong>Q:</strong> how this will work with mirror=True?</p> Container Support - Story #9500 (CLOSED - DUPLICATE): Enable cache in pulp container handlerhttps://pulp.plan.io/issues/95002021-10-11T15:32:22Zipanova@redhat.comipanova@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/496":<a href="https://github.com/pulp/pulp_container/issues/496" class="external">https://github.com/pulp/pulp_container/issues/496</a></p>
<hr>
<p><a href="https://github.com/pulp/pulpcore/commit/81684b206e3fd8bceb104e4a77c0d717387667f9#diff-453fdf3a6e81f92ff5391cf65f9c6154852133a656d82082021e3beaa887776fR194" class="external">https://github.com/pulp/pulpcore/commit/81684b206e3fd8bceb104e4a77c0d717387667f9#diff-453fdf3a6e81f92ff5391cf65f9c6154852133a656d82082021e3beaa887776fR194</a></p>
<p>Pulp Container Registry Handler does not use <code>stream_content</code></p> RPM Support - Issue #9406 (CLOSED - NOTABUG): Trivial OOM on sync for a particular Microsoft repohttps://pulp.plan.io/issues/94062021-09-16T03:33:52Zdalleydalley@redhat.com
<p>Syncing <a href="https://packages.microsoft.com/rhel/8/prod/" class="external">https://packages.microsoft.com/rhel/8/prod/</a> results in an OOM even on a box with ~10gb of available memory</p> RPM Support - Issue #9399 (CLOSED - NOTABUG): sync error: invalid memory alloc request sizehttps://pulp.plan.io/issues/93992021-09-15T09:20:51Zkeilr
<p>pulp version: container image docker.io/pulp/pulp:3.15</p>
<p>remote repository definition:</p>
<pre><code class="text syntaxhl" data-language="text">$ pulp --base-url http://localhost:8080 --username admin --password secret rpm remote show --name "packages-microsoft-com-prod-rhel8"
{
"pulp_href": "/pulp/api/v3/remotes/rpm/rpm/c455d98d-4c8c-446d-aa4d-dffe568675d6/",
"pulp_created": "2021-09-14T14:51:03.146140Z",
"name": "packages-microsoft-com-prod-rhel8",
"url": "https://packages.microsoft.com/rhel/8/prod/",
"ca_cert": null,
"client_cert": null,
"tls_validation": true,
"proxy_url": "http://proxy.example.com:8080",
"pulp_labels": {},
"pulp_last_updated": "2021-09-14T14:51:03.146171Z",
"download_concurrency": null,
"max_retries": null,
"policy": "immediate",
"total_timeout": null,
"connect_timeout": null,
"sock_connect_timeout": null,
"sock_read_timeout": null,
"headers": null,
"rate_limit": null,
"sles_auth_token": null
}
</code></pre>
<p>error:</p>
<pre><code class="text syntaxhl" data-language="text">$ podman logs --follow pulp
pulp [505c8f64043741a7b8f09eac46fa8331]: pulpcore.tasking.pulpcore_worker:INFO: Task a7a26b28-9251-4da1-82ef-19272b6779f0 failed (invalid memory alloc request size 1073741824
)
pulp [505c8f64043741a7b8f09eac46fa8331]: pulpcore.tasking.pulpcore_worker:INFO: File "/usr/local/lib/python3.8/site-packages/pulpcore/tasking/pulpcore_worker.py", line 323, in _perform_task
result = func(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/pulp_rpm/app/tasks/synchronizing.py", line 471, in synchronize
version = dv.create()
File "/usr/local/lib/python3.8/site-packages/pulpcore/plugin/stages/declarative_version.py", line 151, in create
loop.run_until_complete(pipeline)
File "/usr/lib64/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "/usr/local/lib/python3.8/site-packages/pulpcore/plugin/stages/api.py", line 225, in create_pipeline
await asyncio.gather(*futures)
File "/usr/local/lib/python3.8/site-packages/pulpcore/plugin/stages/api.py", line 43, in __call__
await self.run()
File "/usr/local/lib/python3.8/site-packages/pulpcore/plugin/stages/content_stages.py", line 174, in run
await sync_to_async(process_batch)()
File "/usr/local/lib/python3.8/site-packages/asgiref/sync.py", line 444, in __call__
ret = await asyncio.wait_for(future, timeout=None)
File "/usr/lib64/python3.8/asyncio/tasks.py", line 455, in wait_for
return await fut
File "/usr/lib64/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.8/site-packages/asgiref/sync.py", line 486, in thread_handler
return func(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/pulpcore/plugin/stages/content_stages.py", line 122, in process_batch
d_content.content.save()
File "/usr/local/lib/python3.8/site-packages/pulpcore/app/models/base.py", line 149, in save
return super().save(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/django_lifecycle/mixins.py", line 134, in save
save(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/django/db/models/base.py", line 726, in save
self.save_base(using=using, force_insert=force_insert,
File "/usr/local/lib/python3.8/site-packages/django/db/models/base.py", line 763, in save_base
updated = self._save_table(
File "/usr/local/lib/python3.8/site-packages/django/db/models/base.py", line 868, in _save_table
results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
File "/usr/local/lib/python3.8/site-packages/django/db/models/base.py", line 906, in _do_insert
return manager._insert(
File "/usr/local/lib/python3.8/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 1270, in _insert
return query.get_compiler(using=using).execute_sql(returning_fields)
File "/usr/local/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
cursor.execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
</code></pre>
<p>All other repo sync jobs work without problems. (e.g. official rhel(7|8) repos, epel, ...)</p>
<p>Is anyone able to reproduce this MS repo issue?</p> RPM Support - Task #9259 (CLOSED - DUPLICATE): workflow-docs should use pulp-cli instead of httpiehttps://pulp.plan.io/issues/92592021-08-19T14:09:05Zggainey
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2314":<a href="https://github.com/pulp/pulp_rpm/issues/2314" class="external">https://github.com/pulp/pulp_rpm/issues/2314</a></p>
<hr>
<p>Probably shouldn't do this unless/until <strong>all</strong> workflows are supported by pulp-cli commands - mixing pulp-cli and httpie is Very Confusing to the user.</p>
<p>Putting this up as a placeholder for docs-day</p> RPM Support - Issue #9231 (CLOSED - DUPLICATE): The interaction of skip_types and mirror=True is ...https://pulp.plan.io/issues/92312021-08-11T16:19:41Zdalleydalley@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2293":<a href="https://github.com/pulp/pulp_rpm/issues/2293" class="external">https://github.com/pulp/pulp_rpm/issues/2293</a></p>
<hr>
<p>Currently, if mirror=True, the skip_types option is ignored, which was surprising to some users.</p>
<p><a href="https://github.com/pulp/pulp_rpm/blob/052f170fe60f27a32ccbd2d9a42283d7850b80a4/pulp_rpm/app/tasks/synchronizing.py#L1027" class="external">https://github.com/pulp/pulp_rpm/blob/052f170fe60f27a32ccbd2d9a42283d7850b80a4/pulp_rpm/app/tasks/synchronizing.py#L1027</a></p>
<p>Two solutions were proposed:</p>
<ol>
<li>Disallow specifying both options simultaneously (and katello would hide the option from the UI)</li>
<li>Let everything be synced as specified by "mirror", but in the event the sync is an "immediate" mode sync, use deferred_download only for the types which the user requested be skipped, so that the user doesn't pay a disk space cost for them.</li>
</ol>