Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-08-12T14:28:21ZPulp
Planio RPM Support - Issue #9236 (CLOSED - NOTABUG): Pulp 3.14 - can't sync new repositories because of...https://pulp.plan.io/issues/92362021-08-12T14:28:21Zsbrock
<p>Hi there! It seems I've discovered what may be a bug. I've proven this on two separate machines now. Both are fully up to date with Pulp 3.14 and are fresh installs. This seems to be related to issue <a class="issue tracker-1 status-8 priority-6 priority-default closed" title="Issue: Pulp 3.14 - can't sync a repository because of a checksum (CLOSED - NOTABUG)" href="https://pulp.plan.io/issues/9224">#9224</a> but I am not sure.</p>
<p>Syncing new repos fails with checksum validation failure on packages. Which packages it fails on seems random. Each time a new sync occurs, it fails on a different package. Syncing the repo over and over and over again eventually completes successfully, and going forward repo syncs fine. It does not seem to matter where the repository is, as I've tried different mirrors, http and https, and even my local cobbler install. It seems to often occur on the OS and AppStream repositories, and does not matter if its OS or Kickstart. Ive got one on Alma's PowerTools repo as well. This also happens on CentOS, AlmaLinux and RockyLinux. And I've seen it on the EPEL repositories too.</p>
<p>Here's some of the error messages. I am also going to attach a couple of screenshots (with the org fudged out) Let me know what else you need from me, logs, configs, et al. THANKS!!</p>
<p>A file located at the url <a href="https://repo.almalinux.org/almalinux/8.4/PowerTools/x86_64/os/Packages/mingw64-headers-5.0.2-2.el8.noarch.rpm" class="external">https://repo.almalinux.org/almalinux/8.4/PowerTools/x86_64/os/Packages/mingw64-headers-5.0.2-2.el8.noarch.rpm</a> failed validation due to checksum.</p>
<p>A file located at the url <a href="https://repo.almalinux.org/almalinux/8.4/AppStream/x86_64/os/Packages/rust-std-static-1.52.1-1.module_el8.4.0+2520+0729bac9.x86_64.rpm" class="external">https://repo.almalinux.org/almalinux/8.4/AppStream/x86_64/os/Packages/rust-std-static-1.52.1-1.module_el8.4.0+2520+0729bac9.x86_64.rpm</a> failed validation due to checksum.</p>
<p>A file located at the url <a href="http://mirrors.rit.edu/centos/7.9.2009/os/x86_64/Packages/kdeartwork-wallpapers-4.10.5-4.el7.noarch.rpm" class="external">http://mirrors.rit.edu/centos/7.9.2009/os/x86_64/Packages/kdeartwork-wallpapers-4.10.5-4.el7.noarch.rpm</a> failed validation due to checksum.</p>
<p>A file located at the url <a href="http://cobbler" class="external">http://cobbler</a>..org/cobbler/repo_mirror/CentOS_79-x86_64/Packages/thunderbird-68.10.0-1.el7.centos.x86_64.rpm failed validation due to checksum.</p>
<p>A file located at the url <a href="http://cobbler" class="external">http://cobbler</a>..org/cobbler/repo_mirror/EPEL7-x86_64/p/paraview-4.4.0-2.el7.x86_64.rpm failed validation due to checksum.</p>
<p>A file located at the url <a href="http://mirrors.rit.edu/rocky/8.4/BaseOS/x86_64/os/../../../AppStream/x86_64/os/Packages/libkkc-data-0.2.7-12.el8.x86_64.rpm" class="external">http://mirrors.rit.edu/rocky/8.4/BaseOS/x86_64/os/../../../AppStream/x86_64/os/Packages/libkkc-data-0.2.7-12.el8.x86_64.rpm</a> failed validation due to checksum.</p>
<p>A file located at the url <a href="http://mirrors.rit.edu/rocky/8.4/AppStream/x86_64/os/Packages/openblas-0.3.12-1.el8.i686.rpm" class="external">http://mirrors.rit.edu/rocky/8.4/AppStream/x86_64/os/Packages/openblas-0.3.12-1.el8.i686.rpm</a> failed validation due to checksum.</p> RPM Support - Issue #9190 (CLOSED - NOTABUG): Problem syncing rpm-repo for bacula enterprise https://pulp.plan.io/issues/91902021-08-02T07:14:36ZLangesmalle
<p>I'm having a problem syncing the bweb repo from Bacula Enterprise Edition.</p>
<p>For more details, please see:
<a href="https://community.theforeman.org/t/problem-syncing-rpm-repo-for-bacula-enterprise/24679" class="external">https://community.theforeman.org/t/problem-syncing-rpm-repo-for-bacula-enterprise/24679</a></p>
<p>Please find in attachment the repomd.xml file from the Dependencies folder as Sherrill Justin mentioned in his reply.</p>
<p>Please let me know if additional information is required.</p> RPM Support - Issue #8967 (CLOSED - DUPLICATE): "duplicate key value violates unique constraint" ...https://pulp.plan.io/issues/89672021-06-24T13:23:18Zwilful
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2278":<a href="https://github.com/pulp/pulp_rpm/issues/2278" class="external">https://github.com/pulp/pulp_rpm/issues/2278</a></p>
<hr>
<p>The original issue is difficult to reproduce any longer, but there are similar issues which can be. see <a href="https://pulp.plan.io/issues/8967#note-16" class="external">https://pulp.plan.io/issues/8967#note-16</a></p>
<p>========================</p>
<p>Hi for all!</p>
<p>Me need added for pulp server two repositories:</p>
<p><a href="http://downloads.linux.hpe.com/SDR/repo/spp/redhat/7/x86_64/current/" class="external">http://downloads.linux.hpe.com/SDR/repo/spp/redhat/7/x86_64/current/</a></p>
<p><a href="http://downloads.linux.hpe.com/SDR/repo/mcp/CentOS/7/x86_64/current/" class="external">http://downloads.linux.hpe.com/SDR/repo/mcp/CentOS/7/x86_64/current/</a></p>
<p>But i can't do it, becouse:</p>
<pre><code class="text syntaxhl" data-language="text"> "description": "duplicate key value violates unique constraint \"rpm_package_pkgId_key\"\nDETAIL: Key (\"pkgId\")=(ebf96fb31b880280a25d07c596bde204df50d140) already exists.\
n"
</code></pre>
<p>How can I find out in which repository this package is?</p> RPM Support - Story #5117 (CLOSED - CURRENTRELEASE): [Epic] As a user, I can export RPM repositorieshttps://pulp.plan.io/issues/51172019-07-10T19:55:04Zttereshcttereshc@redhat.com
<p>As a user, i can signal the export of some repository version to a file, and have that file saved to disk.</p>
<p>As a user, i can export some repository version, but only include the ‘diff’ of what is different from some other repository version (to get an incremental export)</p>
<p>As a user, I can upload a full export and have its contents be added to an existing repository produce a new repository version.</p>
<p>As a user, i can upload an incremental export and specify a repository version to base it on</p> RPM Support - Story #5112 (CLOSED - CURRENTRELEASE): [Epic] As a user, I can manage auxiliary co...https://pulp.plan.io/issues/51122019-07-10T15:20:32Zttereshcttereshc@redhat.com
<p>Content types to support:<br>
- Group, Category, Environment and Langpacks provided by comps.xml<br>
- custom repodata (unknown to Pulp), yum_repo_metadata_file in Pulp2</p> RPM Support - Story #5111 (CLOSED - WONTFIX): [Epic] As a user, I can calculate applicabilityhttps://pulp.plan.io/issues/51112019-07-10T15:14:23Zttereshcttereshc@redhat.com
<p>There will be a design discussion prior to this ticket being assigned to anyone. The level of effort and the dates for this story can change depending on the outcome, including how much we can [re]use <a href="https://github.com/RedHatInsights/vmaas" class="external">VMaas project</a> for that.</p>
<p>An epic story for applicability calculations, the design for the feature should be outlined here.</p> RPM Support - Story #4762 (CLOSED - CURRENTRELEASE): [Epic] As a user, I can copy contenthttps://pulp.plan.io/issues/47622019-05-02T16:29:43Zdalleydalley@redhat.comRPM Support - Issue #3957 (CLOSED - WONTFIX): on_demand repositories should not allow remove_mis...https://pulp.plan.io/issues/39572018-08-30T17:21:42Zjsherril@redhat.comjsherril@redhat.com
<p>on_demand should always use remove_missing=true because:</p>
<p>1) if a package is removed upstream the on_demand repo won't be able to download it<br>
2) if the checksum of the repo changes, all the old checksum'd packages will still be in the repo and won't be able to be downloaded, nor will the repodata be able to be generated</p> RPM Support - Issue #3682 (CLOSED - WORKSFORME): 'on_demand' download policy not working for SUSE...https://pulp.plan.io/issues/36822018-05-18T12:37:01Zdkliban@redhat.com
<p>A pulp-smash that tests errata for SUSE repos tries to sync a repository using the 'on_demand' policy[0]. However, it seems like this is not working[1] and all the packages are being downloaded during the test.</p>
<p>[0] <a href="https://github.com/PulpQE/pulp-smash/blob/master/pulp_smash/tests/pulp2/rpm/api_v2/test_updateinfo.py#L609" class="external">https://github.com/PulpQE/pulp-smash/blob/master/pulp_smash/tests/pulp2/rpm/api_v2/test_updateinfo.py#L609</a><br>
[1] <a href="https://github.com/pulp/pulp_rpm/pull/1107#pullrequestreview-121264455" class="external">https://github.com/pulp/pulp_rpm/pull/1107#pullrequestreview-121264455</a></p> RPM Support - Issue #2642 (CLOSED - WONTFIX): --auth-ca parameter on repo creation not workinghttps://pulp.plan.io/issues/26422017-03-17T08:58:24Zlenny
<p>Hi,</p>
<p>the --auth-ca parameter creates the local certificate files under /etc/pki/pulp/content, but client requests still verified with the host ca.</p>
<p>You can find the setup on the mailing list: <a href="https://www.redhat.com/archives/pulp-list/2017-March/msg00004.html" class="external">https://www.redhat.com/archives/pulp-list/2017-March/msg00004.html</a></p>
<p>Regards,</p>
<p>Rene</p> RPM Support - Issue #1971 (CLOSED - WONTFIX): '--retain-old-count' option not retroactivehttps://pulp.plan.io/issues/19712016-06-03T17:34:07Zkfiresmithkfiresmith@gmail.com
<p>If you update the '--retain-old-count=' option on a previously sync'd repo that has a number of RPM versions greater than the new value, the new value is not retroactive. Currently it appears the only way you can reduce the number of old versions is to delete the repo and re-create/re-sync with the new target value.</p>
<p>Steps to reproduce:</p>
<p>pulp-admin rpm repo create --repo-id=epel-test --feed=<a href="http://download-i2.fedoraproject.org/pub/epel/5/x86_64/" class="external">http://download-i2.fedoraproject.org/pub/epel/5/x86_64/</a> --retain-old-count=2 && pulp-admin rpm repo sync run --repo-id=epel-test<br>
pulp-admin rpm repo list --details --repo-id=epel-test | grep 'Rpm'</p>
<p>pulp-admin rpm repo update --repo-id=epel-test --retain-old-count=1 && pulp-admin rpm repo sync run --repo-id=epel-test<br>
pulp-admin rpm repo list --details --repo-id=epel-test | grep 'Rpm'</p>
<p>The RPM count will <strong>not</strong> change, but should be reduced by 1/3.</p> RPM Support - Issue #1452 (CLOSED - WONTFIX): _href missing from iso distributorshttps://pulp.plan.io/issues/14522015-12-21T20:52:28ZIchimonji10jerebear@protonmail.com
<p>It's possible to get information about the distributors associated with a repository by issuing either of the following:</p>
<pre><code>GET https://pulp.example.com/pulp/api/v2/repositories/…/?distributors=true
GET https://pulp.example.com/pulp/api/v2/repositories/…/?details=true
</code></pre>
<p>The response body will have a "distributors" attribute, where the attribute is a list of dicts. Unfortunately, the distributors are all missing their `_href` attribute. For example:</p>
<pre><code class="python syntaxhl" data-language="python"><span class="o">>>></span> <span class="kn">import</span> <span class="nn">requests</span>
<span class="o">>>></span> <span class="n">response</span> <span class="o">=</span> <span class="n">requests</span><span class="p">.</span><span class="n">get</span><span class="p">(</span>
<span class="p">...</span> <span class="s">'https://pulp.example.com/pulp/api/v2/repositories/…/distributors=true'</span><span class="p">,</span>
<span class="p">...</span> <span class="s">'…'</span>
<span class="p">...</span> <span class="p">)</span>
<span class="o">>>></span> <span class="n">response</span><span class="p">.</span><span class="n">raise_for_status</span><span class="p">()</span>
<span class="o">>>></span> <span class="n">response</span><span class="p">.</span><span class="n">json</span><span class="p">()[</span><span class="s">'distributors'</span><span class="p">]</span>
<span class="p">[</span>
<span class="p">{</span>
<span class="sa">u</span><span class="s">'_id'</span><span class="p">:</span> <span class="p">{</span><span class="sa">u</span><span class="s">'$oid'</span><span class="p">:</span> <span class="sa">u</span><span class="s">'56786442e779894f7829a5b0'</span><span class="p">},</span>
<span class="sa">u</span><span class="s">'_ns'</span><span class="p">:</span> <span class="sa">u</span><span class="s">'repo_distributors'</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'auto_publish'</span><span class="p">:</span> <span class="bp">True</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'config'</span><span class="p">:</span> <span class="p">{},</span>
<span class="sa">u</span><span class="s">'distributor_type_id'</span><span class="p">:</span> <span class="sa">u</span><span class="s">'iso_distributor'</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'id'</span><span class="p">:</span> <span class="sa">u</span><span class="s">'iso_distributor'</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'last_publish'</span><span class="p">:</span> <span class="bp">None</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'repo_id'</span><span class="p">:</span> <span class="sa">u</span><span class="s">'2c2770dd-3f5a-4bc5-9fae-c37ef873e30f'</span><span class="p">,</span>
<span class="sa">u</span><span class="s">'scheduled_publishes'</span><span class="p">:</span> <span class="p">[]</span>
<span class="p">}</span>
<span class="p">]</span>
</code></pre>
<p>This issue applies to ISO distributors on Pulp 2.7.</p> RPM Support - Issue #982 (CLOSED - NOTABUG): "rpm repo export --start-date" does not generate rep...https://pulp.plan.io/issues/9822015-05-13T17:49:38Zpatrick.wirth
<p>1st, generate a good test with valid repodata</p>
<p>pulp-admin rpm repo create --repo-id=fakepulp \<br>
--feed=<a href="https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/fedora-21/x86_64/" class="external">https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/fedora-21/x86_64/</a><br>
pulp-admin rpm repo sync run --repo-id=fakepulp<br>
pulp-admin rpm repo export run --repo-id=fakepulp<br>
mkdir -p /media/foo</p>
<p>mount -o loop /var/lib/pulp/published/yum/https/exports/repos/fakepulp/fakepulp-2015-05-13T13.01-01.iso /media/foo/</p>
<p>find /media/foo |grep repodata<br>
/media/foo/fakepulp/repodata<br>
/media/foo/fakepulp/repodata/3aeed7b98df3f72c98cfb616e2aab652a4d4881ef16db9e570d0af3f7a9a868e-other.xml.gz<br>
/media/foo/fakepulp/repodata/685a9837d9f328ed161556a85f6f22dc404a0681d73621f31e6b3929d48682d1-updateinfo.xml.gz<br>
/media/foo/fakepulp/repodata/85302be28e0c299568d817859421084d167b1dff01a1dcce9a31861024fc54aa-primary.xml.gz<br>
/media/foo/fakepulp/repodata/c57e62917f1db07c23e89f5cd2ad404d80ed9119cffa9cdac2e72f67f58c5b91-filelists.xml.gz<br>
/media/foo/fakepulp/repodata/dfd6924bc302c3dd52a1cfa2cc36179308e2f03c529828b856c35cae635d90c7-comps.xml<br>
/media/foo/fakepulp/repodata/repomd.xml</p>
<p>Now try and limit the content with --start-date<br>
No repodata will be created for default iso or if specify --export-dir content location</p>
<p>pulp-admin rpm repo export run --repo-id=fakepulp --start-date "2015-03-15T00:00:00"</p>
<p>mount -o loop /var/lib/pulp/published/yum/https/exports/repos/fakepulp/fakepulp-2015-05-13T13.23-01.iso /media/foo/</p>
<p>find /media/foo |grep repodata<br>
no results...</p>
<p>find /media/foo<br>
/media/foo<br>
/media/foo/fakepulp<br>
/media/foo/fakepulp/createrepo-0.9.9-21.2.pulp.fc21.noarch.json<br>
/media/foo/fakepulp/createrepo-0.9.9-21.2.pulp.fc21.noarch.rpm<br>
/media/foo/fakepulp/gofer-2.6.1-1.fc21.noarch.json<br>
/media/foo/fakepulp/gofer-2.6.1-1.fc21.noarch.rpm<br>
/media/foo/fakepulp/gofer-package-2.6.1-1.fc21.noarch.json<br>
/media/foo/fakepulp/gofer-package-2.6.1-1.fc21.noarch.rpm<br>
/media/foo/fakepulp/gofer-system-2.6.1-1.fc21.noarch.json<br>
.<br>
.</p>
<p>No repodata folder or xml data is created which makes it impossible to import this content.</p> RPM Support - Issue #627 (CLOSED - DUPLICATE): --checksum-type does not affect the checksum used ...https://pulp.plan.io/issues/6272015-02-28T22:45:29Zrbarlow
<p>Description of problem:<br>
Setting the --checksum-type on a repo does not seem to have an effect.</p>
<p>Version-Release number of selected component (if applicable):<br>
2.4.3-1</p>
<p>How reproducible:<br>
Every time</p>
<p>Steps to Reproduce:<br>
1. Create a repo, perhaps the zoo repo, setting --checksum-type sha1<br>
2. Sync & Publish</p>
<p>Actual results:<br>
Open the primary.xml.gz file in the published repodata folder. Observe that sha256 was used. For example, I see this tag in the bear package:</p>
<p><checksum pkgid="YES" type="sha256">7a831f9f90bf4d21027572cb503d20b702de8e8785b02c0397445c2e481d81b3</checksum></p>
<p>Expected results:<br>
I expected sha1 to have been used, since I explicitly chose sha1.</p>
<p>Additional info:<br>
I wonder if this is because I sync'd the repo, and perhaps the upstream zoo repo used sha256 and that overrides the --checksum-type flag? I think it's a bug either way, since the --checksum-type flag helptext doesn't list any conditions on whether it gets used.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1167456" class="external">Bugzilla Bug #1167456</a> +</p> RPM Support - Issue #524 (CLOSED - WONTFIX): --fields=pkglist can only be used with --erratum-id ...https://pulp.plan.io/issues/5242015-02-28T22:19:38Zrbarlow
<p>Description of problem:</p>
<p>This command will not print anything:</p>
<p>$ pulp-admin rpm repo content errata --repo-id rhel-6-server --match Type=security --fields pkglist</p>
<p>Neither will this command:</p>
<p>pulp-admin rpm repo content errata --repo-id=rhel-6-server --fields=pkglist --filters='{"issued": {"$gte": "2014-01-01"},"type": "security"}'</p>
<p>However, this command will print the pkglist:</p>
<p>pulp-admin rpm repo content errata --repo-id rhel-6-server --erratum-id RHSA-2014:1075 --fields pkglist</p>
<p>Both commands should print the pkglist.</p>
<p>Version-Release number of selected component (if applicable):<br>
2.4.0-1</p>
<p>How reproducible:<br>
Every time.</p>
<p>Steps to Reproduce:<br>
1. Sync the rhel-6-server repository.<br>
2. Run pulp-admin rpm repo content errata --repo-id rhel-6-server --match Type=security --fields pkglist<br>
3. Also run pulp-admin rpm repo content errata --repo-id=rhel-6-server --fields=pkglist --filters='{"issued": {"$gte": "2014-01-01"},"type": "security"}'</p>
<p>Actual results:<br>
Observe that these commands do not print the pkglist.</p>
<p>Expected results:<br>
The pkglists should be printed for each errata that match a query.</p>
<p>+ This bug was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1141297" class="external">Bugzilla Bug #1141297</a> +</p>