Ok, let me clarify the situation here: this bug needed to be fixed in
order for the message to disappear and the fix has landed a few days
ago. But there is another bug (bug 1070318) which *also* prevents the
message from being properly removed.
Bug 1068843 is currently being worked on and it
** Changed in: maas (Ubuntu Precise)
Status: New = 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/1067929
Title:
maas-region-celeryd connects to the wrong queue.
Ok, let me clarify the situation here: this bug needed to be fixed in
order for the message to disappear and the fix has landed a few days
ago. But there is another bug (bug 1070318) which *also* prevents the
message from being properly removed.
Bug 1068843 is currently being worked on and it
** Changed in: maas (Ubuntu Precise)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage
Marking this verification done as upstream (the bug reporter) thought
that fixing this would also fix the UI message being displayed, however,
that's related to bug #1068843. I've updated the bug description to
accordingly reflect the real issue. Doing so we can simply mark this bug
as
I can say that for me does not disapear.
And the PXE clients boots to a provisioning image and then shuts down
automatically.
--
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
Marking this verification done as upstream (the bug reporter) thought
that fixing this would also fix the UI message being displayed, however,
that's related to bug #1068843. I've updated the bug description to
accordingly reflect the real issue. Doing so we can simply mark this bug
as
I can say that for me does not disapear.
And the PXE clients boots to a provisioning image and then shuts down
automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
The uploading fix appears to be incorrect, as I installed the proposed
update and the issue was not resolved. Marking verification-failed.
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team,
(I wasn't specific, the SRU upload does indeed correct the issues in the
queues line, but celery does not properly connect which is the point of
this SRU.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
The uploading fix appears to be incorrect, as I installed the proposed
update and the issue was not resolved. Marking verification-failed.
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
(I wasn't specific, the SRU upload does indeed correct the issues in the
queues line, but celery does not properly connect which is the point of
this SRU.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Raphaël, or anyone else affected,
Accepted into quantal-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
** 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
** Tags removed: verification-needed
** Tags added: verification-done
--
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.
** Tags removed: verification-done
** Tags added: verification-needed
--
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.
I have a quantal/maas system that was displaying this message. I
upgraded to the version in -proposed (0.1+bzr1269+dfsg-0ubuntu1) and
waited 5 minutes. Unfortunately, the issue persists.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I investigated this and consulted with bigjools, and rvba and this fix
is not related to the meessage of missing images.
** Description changed:
Symptoms
After install, the MAAS interface displays the following warning:
The region controller does not know whether any boot
This bug was fixed in the package maas - 0.1+bzr1269+dfsg-0ubuntu1
---
maas (0.1+bzr1269+dfsg-0ubuntu1) quantal-proposed; urgency=low
* New upstream bugfix release
- Fixes commissioning failing to set memory attribute. (LP: #1064638)
- Fixes node listing by adding
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
--
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
Hello Raphaël, or anyone else affected,
Accepted into quantal-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
** 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
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage
I have a quantal/maas system that was displaying this message. I
upgraded to the version in -proposed (0.1+bzr1269+dfsg-0ubuntu1) and
waited 5 minutes. Unfortunately, the issue persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I investigated this and consulted with bigjools, and rvba and this fix
is not related to the meessage of missing images.
** Description changed:
Symptoms
After install, the MAAS interface displays the following warning:
The region controller does not know whether any boot
This bug was fixed in the package maas - 0.1+bzr1269+dfsg-0ubuntu1
---
maas (0.1+bzr1269+dfsg-0ubuntu1) quantal-proposed; urgency=low
* New upstream bugfix release
- Fixes commissioning failing to set memory attribute. (LP: #1064638)
- Fixes node listing by adding
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To
Hi Thiago,
Maybe, you also need to dpkg-reconfigure maas-cluster-controller
(besides sudo dpkg-reconfigure maas-region-controller) and set the
correct address to communicate to.
Cheers.
** Changed in: maas (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug
Hi Thiago,
There is a background task that should be responsible for cleaning up
the message if no new images are detected, can you please have a look in
/var/log/maas/celery-region.log and confirm that you're seeing the task
being processed all right?
If it is the case, the log file will
Note that the FIX is in the queue... we are waiting for it to be
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/1067929
Title:
maas-region-celeryd connects to the wrong
I have the same.
[2012-10-22 22:23:47,911: INFO/Beat] child process calling self.run()
[2012-10-22 22:23:47,911: INFO/Beat] Celerybeat: Starting...
[2012-10-22 22:23:47,959: INFO/Beat] Scheduler: Sending due task
provisioningserver.tasks.report_boot_images
[2012-10-22 22:28:48,067: INFO/Beat]
Hi Thiago,
Maybe, you also need to dpkg-reconfigure maas-cluster-controller
(besides sudo dpkg-reconfigure maas-region-controller) and set the
correct address to communicate to.
Cheers.
** Changed in: maas (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug
Hi Thiago,
There is a background task that should be responsible for cleaning up
the message if no new images are detected, can you please have a look in
/var/log/maas/celery-region.log and confirm that you're seeing the task
being processed all right?
If it is the case, the log file will
Note that the FIX is in the queue... we are waiting for it to be
released!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage
I have the same.
[2012-10-22 22:23:47,911: INFO/Beat] child process calling self.run()
[2012-10-22 22:23:47,911: INFO/Beat] Celerybeat: Starting...
[2012-10-22 22:23:47,959: INFO/Beat] Scheduler: Sending due task
provisioningserver.tasks.report_boot_images
[2012-10-22 22:28:48,067: INFO/Beat]
Guys,
I created a simple procedure to install MaaS (Ubuntu 12.10) and not hit
this problem... As follows:
1- Create a Virtual Machine with;
* 1024G of RAM
* 1 CPU
* 20G HD
* Ubuntu 12.10 64 bits
* Only ONE Ethernet (most important)
2- Install Ubuntu MaaS Installation (via server CD);
Guys,
I created a simple procedure to install MaaS (Ubuntu 12.10) and not hit
this problem... As follows:
1- Create a Virtual Machine with;
* 1024G of RAM
* 1 CPU
* 20G HD
* Ubuntu 12.10 64 bits
* Only ONE Ethernet (most important)
2- Install Ubuntu MaaS Installation (via server CD);
Yeah...that workaround doesn't seem to work.
--
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
Installation from scratch, file changed to: --queues=celery,master,
message still here even after 2 hours.
MaaS Virtual Machine (KVM test) configuration:
---
2 CPU
1024M
20G of HD
2 ETH (eth0 not used / eth1 default)
---
maas-import-pxe-files executed two times during this test...
MaaS seems
Yeah...that workaround doesn't seem to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage notifications about this bug go
Installation from scratch, file changed to: --queues=celery,master,
message still here even after 2 hours.
MaaS Virtual Machine (KVM test) configuration:
---
2 CPU
1024M
20G of HD
2 ETH (eth0 not used / eth1 default)
---
maas-import-pxe-files executed two times during this test...
MaaS seems
Guys, please, this is annoying... Any news?!
I tried this change: '-Q celery,master' into '--queues=celery,master'
and it does not work... Even after 2 hours...
After, I re-installed MaaS from scratch and I edited that file during
the MaaS Server installation, before GRUB installtion, by
Guys, please, this is annoying... Any news?!
I tried this change: '-Q celery,master' into '--queues=celery,master'
and it does not work... Even after 2 hours...
After, I re-installed MaaS from scratch and I edited that file during
the MaaS Server installation, before GRUB installtion, by
Andres says it was a missing =. It used to say:
--queues celery,master
and he's fixing it to say:
--queues=celery,master
More precisely, the script was using os.execv('celeryd',… , '-Q
celery,master',…) and the space before 'celery' got escaped. I
suggested using the alternative syntax
A workaround is to edit the maas-region-celeryd script (sudo vim
/usr/sbin/maas-region-celeryd) and change: '-Q celery,master' into '
--queues=celery,master'.
Then restart the service:
$ sudo service maas-region-celery restart
--
You received this bug notification because you are a member of
** 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
So, what do you guys recommends?! I have this problem. Ubuntu 12.10, fresh
install MaaS... DHCP and DNS managed by MaaS...
That message does not disappear...
Tks!
Thiago
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
I made the change: '-Q celery,master' into '--queues=celery,master' but the
problem persist.
Please, help!
--
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:
** Changed in: maas (Ubuntu)
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/1067929
Title:
maas-region-celeryd connects to the wrong queue.
This is not fix-released yet, but I can't set it back.
--
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
Sorry guys, status changed by accident.
--
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
Andres says it was a missing =. It used to say:
--queues celery,master
and he's fixing it to say:
--queues=celery,master
More precisely, the script was using os.execv('celeryd',… , '-Q
celery,master',…) and the space before 'celery' got escaped. I
suggested using the alternative syntax
A workaround is to edit the maas-region-celeryd script (sudo vim
/usr/sbin/maas-region-celeryd) and change: '-Q celery,master' into '
--queues=celery,master'.
Then restart the service:
$ sudo service maas-region-celery restart
--
You received this bug notification because you are a member of
** 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
So, what do you guys recommends?! I have this problem. Ubuntu 12.10, fresh
install MaaS... DHCP and DNS managed by MaaS...
That message does not disappear...
Tks!
Thiago
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I made the change: '-Q celery,master' into '--queues=celery,master' but the
problem persist.
Please, help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects
** Changed in: maas (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage
This is not fix-released yet, but I can't set it back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage notifications about
Sorry guys, status changed by accident.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage notifications about this bug go to:
** Changed in: maas (Ubuntu)
Status: New = Incomplete
** Changed in: maas (Ubuntu)
Status: Incomplete = In Progress
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You
** Branch linked: lp:~andreserl/maas/packaging_bzr1269_quantal
--
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
Andres says it was a missing =. It used to say:
--queues celery,master
and he's fixing it to say:
--queues=celery,master
--
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:
** Description changed:
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,
-
** Changed in: maas (Ubuntu)
Status: New = Incomplete
** Changed in: maas (Ubuntu)
Status: Incomplete = In Progress
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Andres Rodriguez (andreserl)
--
You
** Branch linked: lp:~andreserl/maas/packaging_bzr1269_quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
maas-region-celeryd connects to the wrong queue.
To manage notifications
Andres says it was a missing =. It used to say:
--queues celery,master
and he's fixing it to say:
--queues=celery,master
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067929
Title:
** Description changed:
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,
-
68 matches
Mail list logo
