Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-07-20T15:10:49ZPulp
Planio Pulp - Backport #9116 (CLOSED - CURRENTRELEASE): Backport #8779 "Task started on removed worker" ...https://pulp.plan.io/issues/91162021-07-20T15:10:49Zmdellweg
<p>After a postgres outage a couple of tasks were started on workers which logs claim to have been removed. The tasks then got stuck in a 'waiting' state and I had to cancel them to make them go away.</p>
<p>Logs showing worker being removed:</p>
<pre><code>May 19 10:56:34 lxserv2285 rq[589125]: pulp [None]: pulpcore.tasking.worker_watcher:ERROR: Worker '2961917@lxserv2285' has gone missing, removing from list of workers
May 19 10:56:34 lxserv2285 rq[589125]: pulp [None]: pulpcore.tasking.worker_watcher:ERROR: The worker named 2961917@lxserv2285 is missing. Canceling the tasks in its queue.
</code></pre>
<p>Task being started after removal of workers (snippet):</p>
<pre><code>{ "pulp_created": "2021-05-19T10:57:17.819927Z", "state": "waiting",
"worker": "/pulp/api/v3/workers/4d159eb5-01e4-4750-a921-c5b28c411e4a/",
}
</code></pre>
<p>The worker above is the worker that had been removed.</p>
<p>Any idea why the task was started on a worker that should have been removed from the list of workers?</p>
<p>On RHEL8, with
python3-pulpcore-3.11.0-1.el8.noarch</p> Pulp - Issue #9114 (MODIFIED): pulp_database role is incompatible with RHEL7https://pulp.plan.io/issues/91142021-07-19T20:39:28Zmdepaulo@redhat.com
<p>The pulp_database role has logic needed for both centos7 and rhel7 to use the SCL, but it's wrapped in a check for centos 7.</p>
<p>It also includes some centos 7 specific logic.</p> Pulp - Backport #9110 (CLOSED - CURRENTRELEASE): Backport #9000 "On-demand downloading fills up /...https://pulp.plan.io/issues/91102021-07-19T14:11:25Zdalleydalley@redhat.com
<p><a href="https://github.com/pulp/pulpcore/pull/1503" class="external">https://github.com/pulp/pulpcore/pull/1503</a></p> Pulp - Backport #9103 (CLOSED - CURRENTRELEASE): Backport 8295 "Disc Usage during Repository Sync...https://pulp.plan.io/issues/91032021-07-16T20:19:53Zdalleydalley@redhat.com
<p><a href="https://github.com/pulp/pulpcore/pull/1498" class="external">https://github.com/pulp/pulpcore/pull/1498</a></p> Pulp - Issue #9095 (MODIFIED): pulp_installer preflight check is typically not being run when pul...https://pulp.plan.io/issues/90952021-07-15T18:51:43Zmdepaulo@redhat.com
<p>This appears to a regression from <a class="issue tracker-4 status-11 priority-6 priority-default closed child" title="Refactor: Merge the pulp_rpm_prerequisites role into pulp_installer (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/6799">#6799</a> .</p>
<p>It's a bug in the logic, we want to run 2 preflight checks (before and after the prereq_role is loaded).</p>
<p>For the "before" check:</p>
<p>Instead of checking for either pulp-rpm being in <code>pulp_install_plugins</code> (the common use case now) or any plugin having a <code>prereq_role</code> (extremely uncommon now), we check for both of those things happening. We use an "and" rather than an "or".</p>
<p>For the "after" check:</p>
<p>We only check for a plugin having a "prereq_role". We should also check for pulp-rpm being in <code>pulp_install_plugins</code> (the common use case now)</p> Pulp - Issue #9093 (MODIFIED): pulp_installer preflight check fails on EL7 when not installing pu...https://pulp.plan.io/issues/90932021-07-15T18:20:06Zmdepaulo@redhat.com
<p>This seems to be a regression from <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: As an EL7 pulp_installer user, I use a newer version of postgres than 9.6 (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/8154">#8154</a>, which introduced support for installing pulp from the postgres 10 SCL on EL7.</p>
<p>Basically, pip-compile isn't using the postgres 10 SCL's bin folder in the PATH, unlike the pip install commands. So the pip install commands would succeed, and the preflight is falsely blocking the install.</p>
<p>There seems to be a related issue that the preflight command never fails when pulp-rpm is being installed. When pulp-rpm is being installed, we have separate logic for when to fail in the preflight (and there is a bug in that logic.)</p> Pulp - Issue #9089 (MODIFIED): Pulp Installer Does Not Check ipv6 for Nginx Redirect Rulehttps://pulp.plan.io/issues/90892021-07-14T22:29:24Zjamesmarshall24
<p>The nginx.conf.j2 template correctly checks ansible facts for available ipv6 and removes those addresses for listening. However, the 301 redirect for port 80 to 443 does not check for available ipv6 addresses and will always write to that configuration.</p>
<p>This is a follow up to <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: Option to not configure ipv6 listening in nginx config (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/8536">#8536</a></p> Pulp - Backport #9086 (CLOSED - CURRENTRELEASE): Backport #8986 "Double-Crtl-C to pulpcore-worker...https://pulp.plan.io/issues/90862021-07-14T17:22:40Zdalleydalley@redhat.com
<p><a href="https://github.com/pulp/pulpcore/pull/1492" class="external">https://github.com/pulp/pulpcore/pull/1492</a></p> Pulp - Backport #9085 (CLOSED - CURRENTRELEASE): Backport 9070 "Remove Redis from status informat...https://pulp.plan.io/issues/90852021-07-14T15:14:33Zdalleydalley@redhat.com
<p><a href="https://github.com/pulp/pulpcore/pull/1484" class="external">https://github.com/pulp/pulpcore/pull/1484</a></p> Pulp - Backport #9083 (CLOSED - CURRENTRELEASE): Backport 9080 "Invalid relative URLs are not ide...https://pulp.plan.io/issues/90832021-07-14T15:08:09Zdalleydalley@redhat.com
<p><a href="https://github.com/pulp/pulpcore/pull/1480" class="external">https://github.com/pulp/pulpcore/pull/1480</a></p>