Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2016-02-15T08:17:29ZPulp
Planio Pulp - Issue #1675 (CLOSED - WONTFIX): Task cancel does not returns PulpCodedException when task ...https://pulp.plan.io/issues/16752016-02-15T08:17:29Zsbhawsinsbhawsin@redhat.com
<p>The docs string here: <a href="https://github.com/pulp/pulp/blob/master/server/pulp/server/async/tasks.py#L569" class="external">https://github.com/pulp/pulp/blob/master/server/pulp/server/async/tasks.py#L569</a> says that a PulpCodedException should be returned but the cancel tasks simply returns if that task is already in complete state. The doc string should be changed to reflect this</p> Pulp - Issue #1562 (CLOSED - CURRENTRELEASE): Update the command line help text in docs for pulp-...https://pulp.plan.io/issues/15622016-01-20T18:42:14Zsbhawsinsbhawsin@redhat.com
<p>The docs at <a href="https://pulp.readthedocs.org/en/latest/user-guide/admin-client/repositories.html#layout" class="external">https://pulp.readthedocs.org/en/latest/user-guide/admin-client/repositories.html#layout</a> is not updated. The "History" section and "download" command is missing from the command line help text.</p> Pulp - Refactor #1148 (CLOSED - CURRENTRELEASE): Remove 'timed out' state from pulp's task state ...https://pulp.plan.io/issues/11482015-07-23T15:40:42Zsbhawsinsbhawsin@redhat.com
<p>'timed out' state is not used anywhere in the code base but present in the list of completed task states list. It should be removed from the code base as it is no more used.</p>
<p>This state is listed at <a href="https://github.com/pulp/pulp/blob/master/common/pulp/common/constants.py#L47" class="external">https://github.com/pulp/pulp/blob/master/common/pulp/common/constants.py#L47</a>.</p> Pulp - Story #1060 (CLOSED - CURRENTRELEASE): As a user I can run Pulp with multiple celeryBeat i...https://pulp.plan.io/issues/10602015-06-16T21:45:19Zsbhawsinsbhawsin@redhat.com
<p>pulp_celerybeat currently can only be run in one process per deployment, and it is one of the single points of failure in Pulp. Multiple instances of pulp_celerybeat should be able to run concurrently.</p>
<p>Deliverables:</p>
<p>1) Modify Pulp to be able to run multiple pulp_celerybeat process concurrently<br>
2) Ensure that Pulp scheduled calls occur only once even with multiple pulp_celerybeat processes running<br>
3) Ensure that even if pulp_celerybeat processes start being killed, that scheduled calls still dispatch only once.<br>
4) Document changes<br>
5) Add a release note<br>
6) Verify that the failure watcher code is safe to run concurrently<br>
7) Verify that the EventMonitor code is safe to run concurrently<br>
8) Verify that the WorkerTimeoutMonitor code is safe to run concurrently</p> Pulp - Issue #1027 (CLOSED - DUPLICATE): Misleading error message when registering consumer with ...https://pulp.plan.io/issues/10272015-06-03T21:05:38Zsbhawsinsbhawsin@redhat.com
<p>Set verify_ssl: False at all configuration files.</p>
<p>Register a consumer.</p>
<p>[root@localhost pulp]# pulp-consumer register --consumer-id 1<br>
Authentication with username None failed: invalid SSL certificate.</p>
<p>It should actually prompt user to give username and password. The error message is misleading.</p>
<p>[root@localhost pulp]# pulp-consumer -u admin register --consumer-id 1<br>
Enter password:<br>
Consumer [1] successfully registered</p>