[Bug 1067929] Re: maas-region-celeryd connects to the wrong queue.

[Francis J. Lacoste]

** Description changed:

+ Symptoms
+ ========
+ 
+ After install, the MAAS interface displays the following warning:
+ 
+ "The region controller does not know whether any boot images have been
+ imported yet. If this message does not disappear in 5 minutes, there may
+ be a communication problem between the region worker process and the
+ region controller. Check the region worker's logs for signs that it was
+ unable to report to the MAAS API."
+ 
+ Even after 5 minutes and a reload, the the error persisted.
+ 
+ DNS configuration is also broken because of this problem.
+ 
+ 
+ Root Cause
+ ==========
+ 
  maas-region-celeryd connects to 2 queues: ' celery' and 'master'.  The
  problem is obviously the space in front of 'celery'
  
  start_celery() should use something like that instead:
      command = [
          'celeryd',
          '--logfile=%s' % args.logfile,
          '--schedule=%s' % args.schedule,
          '--loglevel=INFO',
          '--beat',
          '--queues=celery,master',
          ]
  
  == TEST ==
  This fix has been tested on both canonistack and in the lenovo lab.

-- 
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/1067929

Title:
  maas-region-celeryd connects to the wrong queue.

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