Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-11-04T07:51:35ZPulp
Planio 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> RPM Support - Story #7665 (CLOSED - DUPLICATE): Related to #7535 - Document how to synchronise re...https://pulp.plan.io/issues/76652020-10-07T12:13:21ZAant
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_rpm/2256":<a href="https://github.com/pulp/pulp_rpm/issues/2256" class="external">https://github.com/pulp/pulp_rpm/issues/2256</a></p>
<hr>
<p>I added a note to <a class="issue tracker-1 status-10 priority-6 priority-default closed" title="Issue: Pulp_rpm sync reports "completed" but does not update packages (CLOSED - WORKSFORME)" href="https://pulp.plan.io/issues/7535">#7535</a> but could not reopen the case.</p>
<p>I created a repo > remote > then synced the repo > publication > distribution.
When I synchronise the repo again, is the distribution expected to contain the new packages?
What is the most efficient way to add the new packages to the distribution, e.g. delete it and create it again?</p>
<p>It looks like the documentation (<a href="https://pulp-rpm.readthedocs.io/en/latest/" class="external">https://pulp-rpm.readthedocs.io/en/latest/</a>) does not anwer these questions.</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> RPM Support - Issue #7321 (CLOSED - CURRENTRELEASE): pulp_rpm: Cannot synchronize repos behind pr...https://pulp.plan.io/issues/73212020-08-14T20:00:40ZAnonymous
<p>I had set up pulpcore and pulp_rpm and had working repos that I had synced successfully.</p>
<p>It stopped working when I upgraded pulp_core from v3.4.2 to v3.5.0.</p>
<p>Interestingly the error message does not mention the remote url the way it is in the remote object.
E.g. for this remote:</p>
<pre><code>{
"pulp_href": "/pulp/api/v3/remotes/rpm/rpm/dcebc720-cec0-440d-8327-605ebefef778/",
"pulp_created": "2020-08-14T19:30:59.442292Z",
"name": "test",
"url": "https://fixtures.pulpproject.org/rpm-unsigned/",
"ca_cert": null,
"client_cert": null,
"client_key": null,
"tls_validation": true,
"proxy_url": http://<my own proxy>,
"username": null,
"password": null,
"pulp_last_updated": "2020-08-14T19:30:59.442315Z",
"download_concurrency": 20,
"policy": "immediate",
"sles_auth_token": null
}
</code></pre>
<pre><code>Aug 14 21:49:42 chsss039 rq[303140]: aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host fixtures.pulpproject.org:443 ssl:default [Connect call failed ('8.43.85.236', 443)]
Aug 14 21:49:42 chsss039 rq[303140]: Traceback (most recent call last):
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa
File "/usr/lib64/python3.6/asyncio/base_events.py", line 794, in create_connection
raise exceptions[0]
File "/usr/lib64/python3.6/asyncio/base_events.py", line 781, in create_connection
yield from self.sock_connect(sock, address)
File "/usr/lib64/python3.6/asyncio/selector_events.py", line 439, in sock_connect
return (yield from fut)
File "/usr/lib64/python3.6/asyncio/selector_events.py", line 469, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
Aug 14 21:49:42 chsss039 rq[303140]: TimeoutError: [Errno 110] Connect call failed ('8.43.85.236', 443)
Aug 14 21:49:42 chsss039 rq[303140]: The above exception was the direct cause of the following exception:
Aug 14 21:49:42 chsss039 rq[303140]: Traceback (most recent call last):
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/rq/worker.py", line 886, in perform_job
rv = job.perform()
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/rq/job.py", line 664, in perform
self._result = self._execute()
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/rq/job.py", line 670, in _execute
return self.func(*self.args, **self.kwargs)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/pulp_rpm/app/tasks/synchronizing.py", line 211, in synchronize
remote_url = fetch_remote_url(remote)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/pulp_rpm/app/tasks/synchronizing.py", line 136, in fetch_remote_url
downloader.fetch()
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/pulpcore/download/base.py", line 160, in fetch
return done.pop().result()
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/pulpcore/download/base.py", line 227, in run
return await self._run(extra_data=extra_data)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/pulp_rpm/app/downloaders.py", line 41, in _run
async with self.session.get(url) as response:
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/client.py", line 1012, in __aenter__
self._resp = await self._coro
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/client.py", line 483, in _request
timeout=real_timeout
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 523, in connect
proto = await self._create_connection(req, traces, timeout)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 859, in _create_connection
req, traces, timeout)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 1004, in _create_direct_connection
raise last_exc
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection
req=req, client_error=client_error)
File "/var/lib/pulp/pulpvenv/lib64/python3.6/site-packages/aiohttp/connector.py", line 943, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
</code></pre>
<p>It seems to be related to the proxy settings. When I try to synchronize I cannot see the traffic on the proxy server.</p>
<p>How to reproduce:</p>
<ul>
<li>On server where pulp is running block outgoing connection (e.g. ip of repo) to repository.</li>
<li>Try to sync remote with proxy_url</li>
</ul> RPM Support - Issue #6859 (CLOSED - NOTABUG): Filter results seems not to work properlyhttps://pulp.plan.io/issues/68592020-05-29T15:01:37Zabrix
<p>Hi,</p>
<p>it seems that the filter does not work as described in the API documentation [1].</p>
<blockquote>
<p>Filter results where name matches value</p>
</blockquote>
<p>I would expect all RPMs to be filtered with the matching name, e.g. "icingabeat".</p>
<pre><code class="text syntaxhl" data-language="text">$ http --body GET http://localhost:24817/pulp/api/v3/content/rpm/packages/ name="icingabeat" |jq -r ".count,.results[].name" |head
32027
icinga-boost-base
icinga-boost-base
icinga2-bin
icinga2-bin
icinga2-bin
icingabeat
icinga2-bin
icinga2-bin
icinga2-bin
$
</code></pre>
<p>Best regards,
Alex</p>
<p>[1] <a href="https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list" class="external">https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_list</a></p> RPM Support - Issue #4826 (CLOSED - WORKSFORME): Pulp RPM Publish Comps File Errorhttps://pulp.plan.io/issues/48262019-05-15T18:45:10ZAnonymous
<p>Hello!</p>
<p>I have had an issue over the last little while since updating several Centos 7 boxes to 2.19. When the repos go to publish it would fail out during "Publishing Comps File" on all repos. Long story short I have tracked it down to a change was made in <a href="https://github.com/pulp/pulp_rpm/blame/2.19-release/plugins/pulp_rpm/plugins/distributors/yum/publish.py" class="external">https://github.com/pulp/pulp_rpm/blame/2.19-release/plugins/pulp_rpm/plugins/distributors/yum/publish.py</a> line 1181-1190. Now that sqliterepo_c is in use instead of createrepo_c (<a href="https://github.com/pulp/pulp_rpm/blame/c5f27803ad26dd8f5ff6c36b7d14f2a95e30ec25/plugins/pulp_rpm/plugins/distributors/yum/publish.py" class="external">https://github.com/pulp/pulp_rpm/blame/c5f27803ad26dd8f5ff6c36b7d14f2a95e30ec25/plugins/pulp_rpm/plugins/distributors/yum/publish.py</a> line 1179), sqliterepo_c doesnt know to look into the ./scratch folder in the job and fails out. More details below.</p>
<p><strong>Problem</strong>:<br>
Running a stock 2.19 on Centos fresh, installed for me hooked up to global repos would sync, but on publish would give the following (I turned on verbose sqliterepo_c output)</p>
<pre><code class="text syntaxhl" data-language="text">[root@test repodata]# pulp-admin rpm repo export run --repo-id centos7-x86_64-os-global
+----------------------------------------------------------------------+
Publishing Repository [centos7-x86_64-os-global]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Initializing repo metadata
[-]
... completed
Publishing Distribution files
[-]
... completed
Publishing RPMs
[==================================================] 100%
10019 of 10019 items
... completed
Publishing Delta RPMs
... skipped
Publishing Errata
[-]
... completed
Publishing Modules
... skipped
Publishing Comps file
[========================================= ] 83%
92 of 110 items
Task Failed
Error occurred during 'sqliterepo_c' execution:
::
15:16:48: Version:
0.10.0
15:16:48: Signal handler setup
15:16:48: cr_get_local_metadata:
/var/cache/pulp/reserved_resource_worker-3@test/96de374b-b164-454d-9c1f-20d6c18e5462/repodata/repomd.xml doesn't
exists
repomd.xml doesn't exist
</code></pre>
<pre><code class="text syntaxhl" data-language="text">May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) Exception caught from plugin during publish for repo [centos7-x86_64-os-global]
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) Traceback (most recent call last):
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 1259, in _do_publish
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) publish_report = publish_repo(transfer_repo, conduit, call_config)
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py", line 737, in wrap_f
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) return f(*args, **kwargs)
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/distributors/export_distributor/distributor.py", line 138, in publish_repo
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) return self._publisher.process_lifecycle()
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/plugins/util/publish_step.py", line 572, in process_lifecycle
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) super(PluginStep, self).process_lifecycle()
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/plugins/util/publish_step.py", line 163, in process_lifecycle
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) step.process()
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/plugins/util/publish_step.py", line 256, in process
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) self._process_block()
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp/plugins/util/publish_step.py", line 303, in _process_block
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) self.process_main()
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) File "/usr/lib/python2.7/site-packages/pulp_rpm/plugins/distributors/yum/publish.py", line 1191, in process_main
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) stderr=stderr)
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) PulpCodedException: Error occurred during 'sqliterepo_c' execution:
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) ::
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184) repomd.xml doesn't exist
May 14 17:32:34 test pulp[472707]: pulp.server.controllers.repository:ERROR: [25c1e177] (472707-25184)
</code></pre>
<p><strong>Fix</strong>:<br>
It should be looking in /var/cache/pulp/reserved_resource_worker-3@test/96de374b-b164-454d-9c1f-20d6c18e5462/scratch/repodata/repomd.xml instead.</p>
<p>I replaced publish.py with the last revision (using createrepo_c) and it worked right away. I also was able to get it to work with sqliterepo_c by adding '/scratch/' to the command. Both tested and gave me a working ISO. :)</p> RPM Support - Story #211 (CLOSED - WONTFIX): [RFE] pulp allows corrupt rpms to be pushed into reposhttps://pulp.plan.io/issues/2112015-02-19T01:12:08ZAnonymous
<p>+<span>+ This bug was initially created as a clone of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1023335" class="external">Bugzilla Bug #1023335</a> +</span>+</p>
<p>Description of problem:</p>
<p>Description of problem:<br>
I create a repo, and push to it a corrupt rpm, which won't install.</p>
<p>Version-Release number of selected component (if applicable):<br>
2.2.0-1</p>
<p>How reproducible:<br>
always</p>
<p>Steps to Reproduce:</p>
<p>1. locate a corrupt rpm:<br>
rpm -K /tmp/corruptrpm-1.0-1.noarch.rpm: RSA sha1 ((MD5) PGP) md5 NOT OK (MISSING KEYS: (MD5) PGP#f44e7eb7)</p>
<p>2. pulp-admin rpm repo create --repo-id test-repo2 --relative-url test-repo2</p>
<p>3. pulp-admin rpm repo uploads rpm -f /tmp/corruptrpm-1.0-1.noarch.rpm --repo-id=test-repo2<br>
<span>----------------------------------------------------------------------</span><br>
Unit Upload<br>
<span><del>--------------------------------------------------------------------</del></span></p>
<p>Extracting necessary metadata for each request...<br>
[==================================================] 100%<br>
Analyzing: corruptrpm-1.0-1.noarch.rpm<br>
... completed</p>
<p>Creating upload requests on the server...<br>
[==================================================] 100%<br>
Initializing: corruptrpm-1.0-1.noarch.rpm<br>
... completed</p>
<p>Starting upload of selected units. If this process is stopped through ctrl+c,<br>
the uploads will be paused and may be resumed later using the resume command or<br>
cancelled entirely using the cancel command.</p>
<p>Uploading: corruptrpm-1.0-1.noarch.rpm<br>
[==================================================] 100%<br>
2729160/2729160 bytes<br>
... completed</p>
<p>Importing into the repository...<br>
... completed</p>
<p>Deleting the upload request...<br>
... completed</p>
<p>Actual results:</p>
<p>Corrult rpm successfully pushed into pulp.</p>
<p>Expected results:</p>
<p>rpm upload should fail due to incorrect checksum</p>
<p>Additional info:</p>
<p>--- Additional comment from <a href="mailto:petter.hassberg@netent.com" class="email">petter.hassberg@netent.com</a> at 10/25/2013 08:49:45 ---</p>
<p>this was not a corrupt rpm after all.</p>
<p>--- Additional comment from <a href="mailto:petter.hassberg@netent.com" class="email">petter.hassberg@netent.com</a> at 11/11/2013 14:49:22 ---</p>
<p>This also is applicable with actual corrupt rpm:s with sha1sum mismatch,.</p>
<p>--- Additional comment from <a href="mailto:skarmark@redhat.com" class="email">skarmark@redhat.com</a> at 11/13/2013 16:56:04 ---</p>
<p>***** Bug 1029085 has been marked as a duplicate of this bug. ***</p> RPM Support - Story #63 (CLOSED - WONTFIX): Errata Applicability Stress Testshttps://pulp.plan.io/issues/632014-12-18T16:12:41ZAnonymousRPM Support - Story #60 (CLOSED - WONTFIX): As an API user, I have documentation describing the I...https://pulp.plan.io/issues/602014-12-18T16:12:41ZAnonymous
<p>We need to document the ISO sync progress report format for API users.</p> RPM Support - Story #58 (CLOSED - WONTFIX): Consumer applicability scalability and performance te...https://pulp.plan.io/issues/582014-12-18T16:12:41ZAnonymousRPM Support - Story #54 (CLOSED - WONTFIX): Client: RPM Bind Command UI Clean Uphttps://pulp.plan.io/issues/542014-12-18T16:12:40ZAnonymousRPM Support - Story #38 (CLOSED - WONTFIX): Yum Plugins: Revisit search indexeshttps://pulp.plan.io/issues/382014-12-18T16:12:38ZAnonymousRPM Support - Story #27 (CLOSED - WONTFIX): Yum Plugins: Resolution for retain-old-count & errata...https://pulp.plan.io/issues/272014-12-18T16:12:37ZAnonymous
<p>Deliverable: decide what needs to happen, but don't write any new code decide if it is ok for --retain-old-count to break availability of RPMs for errata</p> RPM Support - Story #12 (CLOSED - DUPLICATE): As a user, I can upload environment groupshttps://pulp.plan.io/issues/122014-12-18T16:12:35ZAnonymous
<p>Deliverables:</p>
<ul>
<li>yum importer can handle uploads of environment groups</li>
<li>CLI has a command to upload environment groups</li>
</ul> RPM Support - Refactor #5 (CLOSED - WONTFIX): [Task] Make pulp_rpm sync use step processing frame...https://pulp.plan.io/issues/52014-12-18T16:12:34ZAnonymous