Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-12-29T03:40:11ZPulp
Planio Debian Support - Issue #8028 (CLOSED - WORKSFORME): Cannot sync Ubuntu repositorieshttps://pulp.plan.io/issues/80282020-12-29T03:40:11Znhavens
<p>With the following remote configuration, I'm unable to sync to a pulp repository:</p>
<pre><code class="json syntaxhl" data-language="json"><span class="p">{</span><span class="w">
</span><span class="nl">"pulp_href"</span><span class="p">:</span><span class="w"> </span><span class="s2">"/pulp/api/v3/remotes/deb/apt/d5143b62-3f97-4f10-a466-734dcd4d5146/"</span><span class="p">,</span><span class="w">
</span><span class="nl">"pulp_created"</span><span class="p">:</span><span class="w"> </span><span class="s2">"2020-12-29T02:49:24.689377Z"</span><span class="p">,</span><span class="w">
</span><span class="nl">"name"</span><span class="p">:</span><span class="w"> </span><span class="s2">"ubuntu"</span><span class="p">,</span><span class="w">
</span><span class="nl">"url"</span><span class="p">:</span><span class="w"> </span><span class="s2">"http://mirror.us.leaseweb.net/ubuntu"</span><span class="p">,</span><span class="w">
</span><span class="nl">"ca_cert"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"client_cert"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"client_key"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"tls_validation"</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="p">,</span><span class="w">
</span><span class="nl">"proxy_url"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"username"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"password"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"pulp_last_updated"</span><span class="p">:</span><span class="w"> </span><span class="s2">"2020-12-29T03:06:33.546708Z"</span><span class="p">,</span><span class="w">
</span><span class="nl">"download_concurrency"</span><span class="p">:</span><span class="w"> </span><span class="mi">10</span><span class="p">,</span><span class="w">
</span><span class="nl">"policy"</span><span class="p">:</span><span class="w"> </span><span class="s2">"immediate"</span><span class="p">,</span><span class="w">
</span><span class="nl">"total_timeout"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"connect_timeout"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"sock_connect_timeout"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"sock_read_timeout"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"distributions"</span><span class="p">:</span><span class="w"> </span><span class="s2">"bionic bionic-backports bionic-proposed bionic-security bionic-updates"</span><span class="p">,</span><span class="w">
</span><span class="nl">"components"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"architectures"</span><span class="p">:</span><span class="w"> </span><span class="s2">"amd64 i386"</span><span class="p">,</span><span class="w">
</span><span class="nl">"sync_sources"</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="p">,</span><span class="w">
</span><span class="nl">"sync_udebs"</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="p">,</span><span class="w">
</span><span class="nl">"sync_installer"</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span><span class="p">,</span><span class="w">
</span><span class="nl">"gpgkey"</span><span class="p">:</span><span class="w"> </span><span class="kc">null</span><span class="p">,</span><span class="w">
</span><span class="nl">"ignore_missing_package_indices"</span><span class="p">:</span><span class="w"> </span><span class="kc">false</span><span class="w">
</span></code></pre>
<p>I get the following error message:</p>
<pre><code>Dec 28 21:32:42 pulp-server rq[48697]: psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "core_artifact_sha256_key"
Dec 28 21:32:42 pulp-server rq[48697]: DETAIL: Key (sha256)=(e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855) already exists.
</code></pre>
<p>If I subsequently patch the remote to set <code>ignore_missing_package_indices=true</code>, the sync also fails, but with a different error message:</p>
<pre><code>Dec 28 21:36:19 pulp-server rq[48741]: psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "core_contentartifact_content_id_relative_path_d2ef8231_uniq"
Dec 28 21:36:19 pulp-server rq[48741]: DETAIL: Key (content_id, relative_path)=(6bfcee15-6b12-4c36-831d-9b34d1dc9cf8, dists/bionic-backports) already exists.
</code></pre>
<p>I'd be happy to provide full stack traces if that would be helpful.</p> Debian Support - Issue #7756 (CLOSED - WONTFIX): Content upload has different method-definintion ...https://pulp.plan.io/issues/77562020-10-27T15:58:32Zmbucher
<p>Looking at the generated API-Bindings for ruby, the method for creating/uploading a new deb-package differs from the one used for e.g. rpm.</p>
<pre><code class="ruby syntaxhl" data-language="ruby"><span class="k">module</span> <span class="nn">PulpDebClient</span>
<span class="k">class</span> <span class="nc">ContentPackagesApi</span>
<span class="o">...</span>
<span class="k">def</span> <span class="nf">create</span><span class="p">(</span><span class="n">opts</span> <span class="o">=</span> <span class="p">{})</span>
</code></pre>
<p>While in the RPM-bindings it looks like this:</p>
<pre><code class="ruby syntaxhl" data-language="ruby"><span class="k">module</span> <span class="nn">PulpRpmClient</span>
<span class="k">class</span> <span class="nc">ContentPackagesApi</span>
<span class="o">...</span>
<span class="k">def</span> <span class="nf">create</span><span class="p">(</span><span class="n">relative_path</span><span class="p">,</span> <span class="n">opts</span> <span class="o">=</span> <span class="p">{})</span>
</code></pre>
<p>The fact that <code>relative_path</code> is specified as parameter in the latter case seems to be due to the fact that in the API, <code>relative_path</code> is marked as required in pulp_rpm, but not in pulp_deb.</p>
<p><a href="https://pulp-deb.readthedocs.io/en/latest/restapi.html#operation/content_deb_packages_create" class="external">https://pulp-deb.readthedocs.io/en/latest/restapi.html#operation/content_deb_packages_create</a></p>
<p><a href="https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_create" class="external">https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_create</a></p>
<p>THis came up during the <a href="https://github.com/Katello/katello/pull/8632#issuecomment-709563551" class="external">katello integration of pulp_deb for pulpcore</a>.</p> Migration Plugin - Issue #6935 (CLOSED - WONTFIX): Validation failure reports incorrect resources...https://pulp.plan.io/issues/69352020-06-09T12:05:08Zttereshcttereshc@redhat.com
<p><code>rpm_unsigned</code> repo exists, <code>drpm</code> does not.</p>
<p>Migration Plan:</p>
<pre><code class="json syntaxhl" data-language="json"><span class="p">{</span><span class="w"> </span><span class="nl">"plan"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"plugins"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="nl">"type"</span><span class="p">:</span><span class="w"> </span><span class="s2">"rpm"</span><span class="p">,</span><span class="w">
</span><span class="nl">"repositories"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="nl">"name"</span><span class="p">:</span><span class="w"> </span><span class="s2">"rpm_unsigned"</span><span class="p">,</span><span class="w">
</span><span class="nl">"repository_versions"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="nl">"pulp2_repository_id"</span><span class="p">:</span><span class="w"> </span><span class="s2">"rpm_unsigned"</span><span class="p">,</span><span class="w">
</span><span class="nl">"pulp2_distributor_repository_ids"</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="w"> </span><span class="s2">"rpm_unsigned"</span><span class="p">,</span><span class="w"> </span><span class="s2">"drpm"</span><span class="w"> </span><span class="p">]</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">]</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">]</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">]</span><span class="w">
</span><span class="p">}}</span><span class="w">
</span></code></pre>
<p>Result (see the description, it should have onlt <code>drpm</code> there):</p>
<pre><code>$ http :/pulp/api/v3/tasks/7bf152e9-971e-48c4-82a7-9bd8a0ce80fe/
HTTP/1.1 200 OK
Allow: GET, PATCH, DELETE, HEAD, OPTIONS
Connection: Keep-Alive
Content-Length: 1250
Content-Type: application/json
Date: Tue, 09 Jun 2020 10:48:03 GMT
Keep-Alive: timeout=5, max=10000
Server: gunicorn/20.0.4
Vary: Accept,Cookie
X-Frame-Options: SAMEORIGIN
{
"child_tasks": [],
"created_resources": [],
"error": {
"description": "Validation failed: resources missing {'repositories_missing_distributors': ['drpm', 'rpm_unsigned']}",
"traceback": " File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/worker.py\", line 886, in perform_job\n rv = job.perform()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py\", line 664, in perform\n self._result = self._execute()\n File \"/usr/local/lib/pulp/lib64/python3.6/site-packages/rq/job.py\", line 670, in _execute\n return self.func(*self.args, **self.kwargs)\n File \"/home/vagrant/devel/pulp-2to3-migration/pulp_2to3_migration/app/tasks/migrate.py\", line 102, in migrate_from_pulp2\n \"Validation failed: resources missing {}\".format(missing_resources)\n"
},
"finished_at": "2020-06-09T10:47:56.137359Z",
"name": "pulp_2to3_migration.app.tasks.migrate.migrate_from_pulp2",
"parent_task": null,
"progress_reports": [],
"pulp_created": "2020-06-09T10:47:55.933361Z",
"pulp_href": "/pulp/api/v3/tasks/7bf152e9-971e-48c4-82a7-9bd8a0ce80fe/",
"reserved_resources_record": [
"pulp_2to3_migration"
],
"started_at": "2020-06-09T10:47:56.090277Z",
"state": "failed",
"task_group": null,
"worker": "/pulp/api/v3/workers/1b7a3c5f-86f6-4da7-922f-2a61cf6eac56/"
}
</code></pre> Pulp - Task #6588 (CLOSED - WONTFIX): Verify our systemd unit files in pulp_installer CIhttps://pulp.plan.io/issues/65882020-04-28T14:02:35Zmdepaulo@redhat.com
<p>We should run:</p>
<p><code>systemd-analyze verify /path/to/each/unit_file.service</code></p>
<p><a href="https://github.com/systemd/systemd/issues/3677#issuecomment-552143097" class="external">https://github.com/systemd/systemd/issues/3677#issuecomment-552143097</a></p>
<p>However, it will complain about other unit files. Perhaps the dependencies? So we'd have to parse the output.</p> Pulp - Task #6307 (CLOSED - WONTFIX): Add a CentOS 8 upgrade test to the ansible-pulp-cihttps://pulp.plan.io/issues/63072020-03-06T21:27:19Zmdepaulo@redhat.com
<p>This was not done initially during the ansible-pulp CentOS 8 CI implementation due to lack of time.</p>
<p>Even if the version of pulpcore to install is 3.2.0 (or perhaps earlier via <code>pulpcore_version</code>), we should stilll create a pulp-ci image with molecule, and run the "*upgrade" molecule scenarios against it.</p> Pulp - Issue #5985 (CLOSED - WORKSFORME): Status API reports incorrect versions installed for dev...https://pulp.plan.io/issues/59852020-01-14T19:21:29Zbmbouterbmbouter@redhat.com
<p>Using pulplift's box pulp3-source-fedora31 and pulpcore and pulp_file at these versions:</p>
<p>pulpcore==3.0.0<br>
pulp_file==0.1.0</p>
<p>Then I query the status API I sometimes see:</p>
<pre><code> "versions": [
{
"component": "pulpcore",
"version": "3.1.0.dev0"
},
{
"component": "pulp_file",
"version": "0.2.0.dev0"
}
]
</code></pre>
<p>An import from within the virtualenv confirms 3.0.0 is installed with:</p>
<pre><code>$ python
>>> from pulpcore import __version__
>>> __version__
'3.0.0'
</code></pre>
<p>I traced the issue to the way it's checked, there is something it doesn't like about checking it <a href="https://github.com/pulp/pulpcore/blob/c0fcdb7c58fb132c1913f917ac4dc0e7f2c21e59/pulpcore/app/views/status.py#L51" class="external">here</a></p> Migration Plugin - Issue #5374 (CLOSED - WONTFIX): re-run of migration tooling has incorrect countshttps://pulp.plan.io/issues/53742019-08-30T14:08:43Zjsherril@redhat.comjsherril@redhat.com
<p>I synced a repo with ~14K files in pulp2 and then migrated all content to pulp3:</p>
<pre><code>{
"_created": "2019-08-29T18:59:50.347635Z",
"_href": "/pulp/api/v3/tasks/1a1a93c2-dfd6-4ba6-b54e-c74735a3ce5d/",
"created_resources": [],
"error": null,
"finished_at": "2019-08-29T19:01:37.544664Z",
"name": "pulp_2to3_migrate.app.tasks.migrate.migrate_from_pulp2",
"non_fatal_errors": [],
"parent": null,
"progress_reports": [
{
"done": 14444,
"message": "Pre-migrating Pulp 2 ISO content (general info)",
"state": "completed",
"suffix": null,
"total": 14447
},
{
"done": 14444,
"message": "Pre-migrating Pulp 2 ISO content (detail info)",
"state": "completed",
"suffix": null,
"total": 14447
},
{
"done": 14051,
"message": "Migrating ISO content to Pulp 3",
"state": "completed",
"suffix": null,
"total": 14453
},
{
"done": 14453,
"message": "Migrating content to Pulp 3",
"state": "completed",
"suffix": null,
"total": 14453
}
],
"reserved_resources_record": [
"pulp_2to3_migration"
],
"spawned_tasks": [],
"started_at": "2019-08-29T18:59:50.474079Z",
"state": "completed",
"worker": "/pulp/api/v3/workers/75176664-9633-46f5-8989-456923ba333a/"
}
</code></pre>
<p>the task counts here looked correct. I then re-ran the migration without any changes, and it looked like this:</p>
<pre><code>{
"_created": "2019-08-29T19:24:08.615486Z",
"_href": "/pulp/api/v3/tasks/eee0440a-0d46-48f8-8d3b-2bf711b7b0c4/",
"created_resources": [],
"error": null,
"finished_at": "2019-08-29T19:24:11.410935Z",
"name": "pulp_2to3_migrate.app.tasks.migrate.migrate_from_pulp2",
"non_fatal_errors": [],
"parent": null,
"progress_reports": [
{
"done": 390,
"message": "Migrating ISO content to Pulp 3",
"state": "completed",
"suffix": null,
"total": 402
},
{
"done": 402,
"message": "Migrating content to Pulp 3",
"state": "completed",
"suffix": null,
"total": 402
},
{
"done": 0,
"message": "Pre-migrating Pulp 2 ISO content (general info)",
"state": "completed",
"suffix": null,
"total": 0
},
{
"done": 0,
"message": "Pre-migrating Pulp 2 ISO content (detail info)",
"state": "completed",
"suffix": null,
"total": 0
}
],
"reserved_resources_record": [
"pulp_2to3_migration"
],
"spawned_tasks": [],
"started_at": "2019-08-29T19:24:08.732119Z",
"state": "completed",
"worker": "/pulp/api/v3/workers/75176664-9633-46f5-8989-456923ba333a/"
}
</code></pre>
<p>the counts for that first progress_report appears incorrect</p> Pulp - Story #5254 (CLOSED - WONTFIX): mirror mode cannot be set on a remotehttps://pulp.plan.io/issues/52542019-08-12T20:52:58Zjsherril@redhat.comjsherril@redhat.com
<p>The various remotes do not support setting the 'mirror' mode, it was removed as part of: <a href="https://pulp.plan.io/issues/3492" class="external">https://pulp.plan.io/issues/3492</a></p>
<p>I had expressed some concern here: <a href="https://www.redhat.com/archives/pulp-dev/2018-March/msg00058.html" class="external">https://www.redhat.com/archives/pulp-dev/2018-March/msg00058.html</a><br>
but it seemed to not get any attention. In the meantime it sees that download policy was added back to the remotes.</p> RPM Support - Issue #4693 (CLOSED - WONTFIX): Module Streams not copying correctly with recursive...https://pulp.plan.io/issues/46932019-04-15T20:25:03Zpaji@redhat.compaji@redhat.com
<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 #4461 (CLOSED - WONTFIX): As a user i can configure download of the fore...https://pulp.plan.io/issues/44612019-02-25T14:22:27Zbherring
<p>Some images like windows base images, contain artifacts whose distribution is restricted by license.<br>
When these images are pushed to a registry, restricted artifacts are skipped/not included by default.</p>
<p>These artifacts are called foreign layers and have "mediaType": "application/vnd.docker.image.rootfs.foreign.diff.tar.gzip"</p>
<p>Remote should have a Boolean "*allow_foreign_layers*" option which would control the download of the foreign layers.</p>
<p><strong>Set to False (default):</strong><br>
Pulp will check the mediatype and simply will skip the foreign layers.<br>
Case: do not sync content which is restricted by a license without explicit acknowledgment in the Remote config<br>
From client side, it will follow the url specified in the details of the layer in the manifest.</p>
<p><strong>Set to True:</strong><br>
Pulp will download the foreign layers by following the url.<br>
Case: due to use case of registries with air gaped network, now it's possible to push to the registry foreign layers, by enabling -allow-nondistributable-artifacts daemon option. From client side, foreign layers are now pulled from the registry if possible, falling back to the URLs in the image manifest otherwise. As far as i know that's done in docker for Windows. Linux version is still ignoring foreign layers during pull.</p> Debian Support - Task #4150 (CLOSED - WONTFIX): The pool folder structure could be improvedhttps://pulp.plan.io/issues/41502018-11-13T12:22:48Zquba42
<p>When publishing Debian repositories we currently use the following 'pool' folder structure:</p>
<pre><code class="text syntaxhl" data-language="text"><repo_base>/pool/<component>/<files>
</code></pre>
<p>For components like 'main' in Debian this leads to a huge number of files in a single folder.</p>
<p>For this reason the upstream Debian repositories use (one of) the following 'pool' folder structures:</p>
<pre><code class="text syntaxhl" data-language="text"><repo_base>/pool/<component>/<first_char_of_binary_package_name>/<binary_package_name>/<files>
<repo_base>/pool/<component>/lib<fourth_char_of_binary_package_name>/lib<rest_of_binary_package_name>/<files>
</code></pre>
<p>Once the refactoring from <a href="https://github.com/pulp/pulp_deb/pull/57" class="external">https://github.com/pulp/pulp_deb/pull/57</a> is merged, it would be relatively trivial to implement the same pool folder structure Debian uses in pulp_deb.</p> File Support - Task #3823 (CLOSED - WONTFIX): Analyze repository version creation performance for...https://pulp.plan.io/issues/38232018-07-06T16:40:45Zdkliban@redhat.com
<p>After the user has migrated content from Pulp 2 to Pulp 3, it will be necesary to migrate the repositories and the association between repos and content. There are 2 options for migrating the association:</p>
<p>- create a repository version by performing a sync from Pulp 2 repository<br>
- create a repository version by querying Pulp 2, find units in Pulp 3, create a repository version by specifying the pulp 3 units.</p>
<p>This task is to analyze the performance of the two methods of creating repository versions and provide guidance on how this part of the migration should be handled.</p> RPM Support - Story #3779 (CLOSED - WONTFIX): As a user, I want to publish/export Text-Only erratahttps://pulp.plan.io/issues/37792018-06-21T17:43:50Zttereshcttereshc@redhat.com
<p>Pulp filters out errata without packages during publish.<br>
So between remote source and publish result there can be difference in the number of errata.<br>
These errata will never be shown as applicable, it's informative in case someone reads it.</p>
<p>Example of text-only errata:<br>
- when container image is released<br>
- when packages getting deprecated in that repo are announced</p>
<p>These errata don't have any RPM packages associated with them.</p>
<p>Current behaviour is not a bug and such errata are filtered out on purpose.<br>
When implementing this RFE, make sure to distinguish between an erratum which has never had packages in its pkglist and an erratum which doesn't have packages because they are not present in a repo.</p> Pulp - Story #3396 (CLOSED - WONTFIX): Build a plugin writer's Docker image and publish it on Doc...https://pulp.plan.io/issues/33962018-02-26T21:54:38Zmansari
<p><a href="https://hub.docker.com/" class="external">Docker Hub</a> is a cloud-based registry service which allows you to store manually pushed Docker images. This task is to have the ability to build a Docker image that has the following:</p>
<p>1. Built on a clean official Fedora F27 image.<br>
2. A non-source checkout of pulpcore installed on it. This will be installed using the published playbooks on galaxy<br>
3. Add a nice welcome screen with motd indicating that they should install a plugin, run its migrations, or consider making a plugin with the Pulp dev guide.</p>
<p>Once done building the image, if it was built successfully, the build code will push the image to Docker Hub.</p>
<p>The user account name on docker hub should be 'pulp' and the name of this image should be 'pulpcore'. This task includes registering the account on Docker Hub and responsibly storing the credentials.</p>
<p>This image should be compatible with Vagrant needs so that it can work in congruence with our custom <a href="https://github.com/pulp/devel/blob/3.0-dev/Vagrantfile.example" class="external">Vagrantfile</a></p> Pulp - Issue #3382 (CLOSED - WONTFIX): listing tasks with pulp-admin -vvv returns incorrect infor...https://pulp.plan.io/issues/33822018-02-17T20:51:09Zdalleydalley@redhat.com
<p>This is a similar issue to the recent worker_name issue, but it only applies to the list view</p>
<p>pulp-admin -vvv tasks list --all</p>
<pre><code>[
......
{
"exception": null,
"task_type": null,
"_href": "/pulp/api/v2/tasks/2c45e8a8-b796-47a3-8130-c1288a9e5ed2/",
"task_id": "2c45e8a8-b796-47a3-8130-c1288a9e5ed2",
"tags": [
"pulp:repository:zoo",
"pulp:action:publish"
],
"finish_time": "2018-02-17T20:45:15Z",
"_ns": "task_status",
"start_time": "2018-02-17T20:45:15Z",
"traceback": null,
"spawned_tasks": [],
"progress_report": {},
"state": "finished",
"worker_name": "reserved_resource_worker-0@pulp2.dev",
"result": null,
"error": null,
"_id": {
"$oid": "5a88945bc7fdea845d0b29c7"
},
"id": "5a88945bc7fdea845d0b29c7"
}
]
</code></pre>
<p>pulp-admin -vvv tasks details --task-id 2c45e8a8-b796-47a3-8130-c1288a9e5ed2</p>
<pre><code> {
"exception": null,
"task_type": "pulp.server.managers.repo.publish.publish",
"_href": "/pulp/api/v2/tasks/2c45e8a8-b796-47a3-8130-c1288a9e5ed2/",
"task_id": "2c45e8a8-b796-47a3-8130-c1288a9e5ed2",
"tags": [
"pulp:repository:zoo",
"pulp:action:publish"
],
"finish_time": "2018-02-17T20:45:15Z",
"_ns": "task_status",
"start_time": "2018-02-17T20:45:15Z",
"traceback": null,
"spawned_tasks": [],
"progress_report": {},
"queue": "reserved_resource_worker-0@pulp2.dev.dq2",
"state": "finished",
"worker_name": "reserved_resource_worker-0@pulp2.dev",
"result": {
"exception": null,
"repo_id": "zoo",
"started": "2018-02-17T20:45:15Z",
"_ns": "repo_publish_results",
"completed": "2018-02-17T20:45:15Z",
"traceback": null,
"distributor_type_id": "yum_distributor",
"error_message": null,
"summary": "Skipped: Repository content has not changed since last publish.",
"result": "skipped",
"distributor_id": "yum_distributor",
"id": "5a88945b30f2524eb69dbd81",
"details": "Skipped: Repository content has not changed since last publish."
},
"error": null,
"_id": {
"$oid": "5a88945bc7fdea845d0b29c7"
},
"id": "5a88945bc7fdea845d0b29c7"
}
</code></pre>