[Pulp-list] Can't Delete Repo

[Brian Bouterse]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Ben,

The tasking system was significantly improved with 2.6.x versus 2.5.x,
but here are some recommendations that you can use on 2.5.x.

use pulp-admin to list tasks:  `pulp-admin tasks list`. The list is
long and the ordering isn't as you probably would expect so make sure
to look at it all. You should look for tasks in the running state and
manually cancel them by uuid with `pulp-admin tasks cancel --task-id`.

Also gratuitously restarting pulp_workers and pulp_resource_manager
may help as it does similar cancellations.

I expect after either these actions, new pulp tasks should execute
correctly.

- -Brian


On 04/30/2015 03:53 AM, ben.stanley at exemail.com.au wrote:
> Hello Pulp Team,
> 
> I have a large pulp server configured here, with 577 repos.
> 
> Unfortunately, some of my repos have been created in error, and I
> must delete them. However, when I attempt to delete them, the
> command shows only this:
> 
> ----------------------------------------------------------------------
- -
>
> 
# pulp-admin rpm repo delete --repo-id=atrpms-7-i386-bleeding
> This command may be exited via ctrl+c without affecting the
> request.
> 
> 
> [-] Running... [|] Waiting to begin... 
> ----------------------------------------------------------------------
- -
>
>  It doesn't get anywhere.
> 
> The pulp.log file shows that the delete request is created, but
> doesn't seem to do anything about it. 
> ------------------------------- pulp.log
> ------------------------------ Apr 30 17:01:15 bumblebee pulp:
> celery.worker.strategy:INFO: Received task: 
> pulp.server.async.tasks._reserve_resource[bcc293de-7f91-4df1-bf62-b4fb
7a98feef]
>
> 
Apr 30 17:01:16 bumblebee pulp: celery.worker.job:INFO: Task
> pulp.server.async.tasks._reserve_resource[bcc293de-7f91-4df1-bf62-b4fb
7a98feef]
>
> 
succeeded in 0.0414823299507s:
> u'reserved_resource_worker-3 at bumblebee.rydalmere.corpnet.dq' Apr 30
> 17:01:16 bumblebee pulp: celery.worker.strategy:INFO: Received 
> task: 
> pulp.server.tasks.repository.delete[8e13325a-f23a-4f6f-9342-0fc381ae10
77]
>
> 
- -----------------------------------------------------------------------
> 
> If I stop pulp and re-start it 
> ----------------------------------------------------------------------
- -
>
> 
for SERVICE in {pulp_resource_manager,pulp_celerybeat,pulp_workers,mongo
d}
> do systemctl stop ${SERVICE} done
> 
> for SERVICE in
> {mongod,pulp_workers,pulp_celerybeat,pulp_resource_manager} do 
> systemctl start ${SERVICE} done 
> ----------------------------------------------------------------------
- -
>
>  Then in the pulp.log file I see 549 "Received task" messages: 
> ---------------------------- pulp.log
> --------------------------------- Apr 30 16:49:46 bumblebee pulp:
> celery.worker.strategy:INFO: Received task: 
> pulp.server.tasks.repository.sync_with_auto_publish[73f1e008-57d0-4664
- -afb7-1b9b7e45249d]
>
> 
Apr 30 16:49:46 bumblebee pulp: celery.worker.strategy:INFO: Received
> task: 
> pulp.server.async.tasks._queue_release_resource[2a1d2953-d03f-46c4-891
4-8b784918da7a]
>
> 
Apr 30 16:49:46 bumblebee pulp: celery.worker.strategy:INFO: Received
> task: 
> pulp.server.tasks.repository.sync_with_auto_publish[d5ee420b-5d2a-4888
- -a2b4-3c7da5d1b0dc]
>
> 
Apr 30 16:49:46 bumblebee pulp: celery.worker.strategy:INFO: Received
> task: 
> pulp.server.tasks.repository.sync_with_auto_publish[e629238c-6608-4587
- -87db-3f0d40aa5629]
>
> 
Apr 30 16:49:46 bumblebee pulp: celery.worker.strategy:INFO: Received
> task: 
> pulp.server.async.tasks._queue_release_resource[a318fe17-dc1a-41e3-bd6
5-7517e6df9119]
>
> 
Apr 30 16:49:46 bumblebee pulp: celery.worker.strategy:INFO: Received
> task: 
> pulp.server.managers.repo.publish.publish[05879c29-3941-40b8-a912-05e0
a0056b0a]
>
> 
<lots more snipped out>
> ----------------------------------------------------------------------
- -
>
> 
Please find more complete log information attached to this email.
> 
> In my understanding, the deletion task is probably being blocked
> by another task using the repo. How can I find out what is causing
> the blockage? How can I un-block it? What can I do to make the repo
> deletion succeed?
> 
> I have the following software: 
> ----------------------------------------------------------------------
- -
>
> 
pulp-rpm-plugins-2.5.1-1.el7.noarch
> python-pulp-bindings-2.5.1-1.el7.noarch 
> pulp-puppet-admin-extensions-2.5.1-1.el7.noarch 
> python-isodate-0.5.0-4.pulp.el7.noarch 
> python-kombu-3.0.15-12.pulp.el7.noarch 
> pulp-admin-client-2.5.1-1.el7.noarch 
> python-pulp-rpm-common-2.5.1-1.el7.noarch 
> pulp-puppet-plugins-2.5.1-1.el7.noarch 
> python-pulp-common-2.5.1-1.el7.noarch 
> pulp-rpm-admin-extensions-2.5.1-1.el7.noarch 
> python-pulp-puppet-common-2.5.1-1.el7.noarch 
> pulp-selinux-2.5.1-1.el7.noarch pulp-server-2.5.1-1.el7.noarch 
> python-pulp-client-lib-2.5.1-1.el7.noarch 
> ----------------------------------------------------------------------
- -
>
> 
I know these aren't the latest, but I can't update pulp until I can solv
e
> getting pulp to update its repos [1].
> 
> 
> Thanks, Ben Stanley.
> 
> [1] I installed pulp on workstation, but now there is a dependency
> from python-mongoengine to python-blinker, which is only available
> in server, which I don't have yet, and pulp isn't updating well at
> the moment, which is likely related to the 549 tasks it runs
> whenever I re-start it.
> 
> 
> 
> _______________________________________________ Pulp-list mailing
> list Pulp-list at redhat.com 
> https://www.redhat.com/mailman/listinfo/pulp-list
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVQkz6AAoJEK48cdELyEfyA0UH/1wWJbDxx0s7Uf2XdKZwLXqm
rNZml9yFCeqwCzCF4kNLhvh2nFFF6gybkBdcY2LlCH0PpIU37g40ILo8ZI/RgLtY
B2BK2lgfVi9djAZE34deMdtmJ6rz8HVDmU+Ue6uMc01B82+LCFAPIBWE41WCY2j2
LyPHNlpsey7qH/xjrRtZ/asva6tEV0kqMqcAy0Yp8d1gCRGsVUZ09WkEOCv968tk
FJ/UWP1nph3lt39spPAF44fL4bt0B3/OtqAi/Efc8rv27jATAfo5cnqWBLSHCsZU
DfDSn0mWMOu24vxdz0M6qN+r6f2zvGx7zuaBzTHHcvx6PRVzk3LpFhMCqh55qTQ=
=hQuf
-----END PGP SIGNATURE-----