[Bug 1059453] Re: The celery cluster worker is not properly stopped
** Changed in: maas (Ubuntu) Status: Triaged = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
** Changed in: maas Status: Fix Committed = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
** Changed in: maas Assignee: (unassigned) = Jeroen T. Vermeulen (jtv) ** Changed in: maas Status: Triaged = In Progress -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
** Branch linked: lp:~jtv/maas/bug-1059453 -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
** Changed in: maas Status: In Progress = Fix Committed -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
Update for the record. As we have since found out, it's much worse than just needing an expect fork. Somewhere along the line, before it gets around to running the start-cluster-controller code proper, maas- provision does a whole bunch of other forks. The question is whether we can make upstart track the right child process. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1059453] Re: The celery cluster worker is not properly stopped
On Wednesday 03 October 2012 02:47:05 you wrote: Update for the record. As we have since found out, it's much worse than just needing an expect fork. Somewhere along the line, before it gets around to running the start-cluster-controller code proper, maas- provision does a whole bunch of other forks. The question is whether we can make upstart track the right child process. The answer to fix this is to make a completely new wrapper script outside of maas-provision, I think. There's some weirdness going on in it. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1059453] Re: The celery cluster worker is not properly stopped
I suspect there's a expect fork missing in the upstart conf ** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Status: New = Triaged ** Changed in: maas Importance: Undecided = Critical -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
