| 2012-10-17 23:22:20 |
Raphaël Badin |
bug |
|
|
added bug |
| 2012-10-17 23:22:30 |
Raphaël Badin |
affects |
maas |
maas (Ubuntu) |
|
| 2012-10-17 23:27:47 |
Andres Rodriguez |
maas (Ubuntu): status |
New |
Incomplete |
|
| 2012-10-17 23:27:52 |
Andres Rodriguez |
maas (Ubuntu): status |
Incomplete |
In Progress |
|
| 2012-10-17 23:27:54 |
Andres Rodriguez |
maas (Ubuntu): importance |
Undecided |
Critical |
|
| 2012-10-17 23:27:57 |
Andres Rodriguez |
maas (Ubuntu): assignee |
|
Andres Rodriguez (andreserl) |
|
| 2012-10-18 00:13:49 |
Launchpad Janitor |
branch linked |
|
lp:~andreserl/maas/packaging_bzr1269_quantal |
|
| 2012-10-18 00:19:21 |
Andres Rodriguez |
description |
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',
] |
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. |
|
| 2012-10-18 07:12:27 |
Raphaël Badin |
maas (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2012-10-18 14:47:55 |
Francis J. Lacoste |
description |
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. |
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. |
|
| 2012-10-19 05:12:43 |
Thiago Martins |
maas (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2012-10-20 15:04:07 |
Alex Wauck |
bug |
|
|
added subscriber Alex Wauck |
| 2012-10-22 09:30:21 |
Andres Rodriguez |
maas (Ubuntu): status |
Fix Released |
Fix Committed |
|
| 2012-10-22 14:17:15 |
Nick Moffitt |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2012-10-23 08:29:11 |
Dave Walker |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-10-23 08:29:15 |
Dave Walker |
bug |
|
|
added subscriber SRU Verification |
| 2012-10-23 08:29:17 |
Dave Walker |
tags |
|
verification-needed |
|
| 2012-10-23 08:49:20 |
Andres Rodriguez |
description |
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. |
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 ==
1. Install maas
2. run maas-import-pxe-files.
3. make sure message about missing pxe files disappears after 5 mins. |
|
| 2012-10-23 10:04:28 |
Andres Rodriguez |
tags |
verification-needed |
verification-done |
|
| 2012-10-23 10:49:28 |
Andres Rodriguez |
tags |
verification-done |
verification-needed |
|
| 2012-10-23 16:07:11 |
Andres Rodriguez |
description |
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 ==
1. Install maas
2. run maas-import-pxe-files.
3. make sure message about missing pxe files disappears after 5 mins. |
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 ==
1. Install maas
2. run maas-import-pxe-files.
3. in /var/log/maas/celery-region.log search:
[2012-10-23 18:02:19,037: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.report_boot_images
[2012-10-23 18:02:19,052: INFO/MainProcess] Got task from broker: provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561]
[2012-10-23 18:02:19,087: INFO/MainProcess] Task provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561] succeeded in 0.00621294975281s: None |
|
| 2012-10-23 16:09:00 |
Andres Rodriguez |
tags |
verification-needed |
verification-done |
|
| 2012-10-23 16:51:09 |
Launchpad Janitor |
maas (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2012-10-23 20:56:38 |
Andres Rodriguez |
nominated for series |
|
Ubuntu Precise |
|
| 2012-10-23 20:56:38 |
Andres Rodriguez |
bug task added |
|
maas (Ubuntu Precise) |
|
| 2012-10-24 22:25:29 |
Michael Casadevall |
tags |
verification-done |
verification-failed |
|
| 2012-10-25 07:42:02 |
Andres Rodriguez |
description |
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 ==
1. Install maas
2. run maas-import-pxe-files.
3. in /var/log/maas/celery-region.log search:
[2012-10-23 18:02:19,037: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.report_boot_images
[2012-10-23 18:02:19,052: INFO/MainProcess] Got task from broker: provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561]
[2012-10-23 18:02:19,087: INFO/MainProcess] Task provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561] succeeded in 0.00621294975281s: None |
Symptoms
========
DNS configuration is broken because of this problem.
In /var/log/maas/celery-region.log search for
[2012-10-23 18:02:19,037: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.report_boot_images
[2012-10-23 18:02:19,052: INFO/MainProcess] Got task from broker: provisioningserver.tasks.report_boot_images
[2012-10-23 18:02:19,087: INFO/MainProcess] Task provisioningserver.tasks.report_boot_images
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 ==
1. Install maas
2. run maas-import-pxe-files.
3. in /var/log/maas/celery-region.log search:
[2012-10-23 18:02:19,037: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.report_boot_images
[2012-10-23 18:02:19,052: INFO/MainProcess] Got task from broker: provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561]
[2012-10-23 18:02:19,087: INFO/MainProcess] Task provisioningserver.tasks.report_boot_images[045a83ac-64a2-448b-ada3-f82131b56561] succeeded in 0.00621294975281s: None |
|
| 2012-10-25 07:42:09 |
Andres Rodriguez |
tags |
verification-failed |
verification-done |
|
| 2012-10-26 13:16:11 |
Dave Walker |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-10-26 13:52:32 |
Dave Walker |
maas (Ubuntu Precise): status |
New |
Fix Released |
|
| 2012-10-28 14:24:04 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/maas |
|
