[Bug 1059453] [NEW] The celery cluster worker is not properly stopped

Raphaël Badin 1059453 at bugs.launchpad.net
Mon Oct 1 08:59:46 UTC 2012


Public bug reported:

The celery cluster is started in
upstream:src/provisioningserver/start_cluster_controller.py, called from
the upstart script packaging:debian/maas-cluster-controller.maas-
cluster-celery.upstart.  When all the MAAS' services are stopped (for
instance when all the MAAS packages are purged), the celery workers are
not properly stopped.

How to recreate:
- install the MAAS package
- run `ps aux | grep celeryd` to get the list of all the celeryd services. After the synchronization phase, you should see the region workers and the cluster workers (http://paste.ubuntu.com/1253472/ the region workers listen to 'celery' and 'master' while the cluster workers listen to a queue named after a UUID)
- remove all the packages with 'sudo apt-get purge maas*'
- run `ps aux | grep celeryd`:  the cluster workers are still running.

** Affects: maas
     Importance: Critical
         Status: Triaged

** Affects: maas (Ubuntu)
     Importance: Critical
         Status: Triaged

** Project changed: maas => maas (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1059453

Title:
  The celery cluster worker is not properly stopped

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1059453/+subscriptions



More information about the Ubuntu-server-bugs mailing list