'write_dhcp_config' tasks are not executed in order
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | MAAS |
High
|
Unassigned | ||
Bug Description
The execution of the Celery tasks in general and the 'write_dhcp_config' tasks in particular is done in no particular order. The result is that if a user configures a cluster twice with different settings (say he configures it once, makes a mistake and then configure it twice), there is no guarantee about which task will be executed first and thus the last executed 'write_dhcp_config' task might be the first one sent (the one with the mistake).
| summary: |
- Multiple write_dhcp_config tasks are not executed in order + 'write_dhcp_config' tasks are not executed in order |
| Gavin Panella (allenap) wrote : | #1 |
| tags: | added: celery |
| Julian Edwards (julian-edwards) wrote : Re: [Bug 1324943] Re: 'write_dhcp_config' tasks are not executed in order | #2 |
On 31/05/14 00:22, Gavin Panella wrote:
> We will be dropping Celery from MAAS this cycle, so hopefully this won't
> be a problem for long.
>
Eh what? When/who decided that?
| Gavin Panella (allenap) wrote : | #3 |
On 2 June 2014 01:19, Julian Edwards <email address hidden> wrote:
> On 31/05/14 00:22, Gavin Panella wrote:
>> We will be dropping Celery from MAAS this cycle, so hopefully this won't
>> be a problem for long.
>
> Eh what? When/who decided that?
Agreed with Mark in Austin. He was pushing for it, and (I think) gmb,
rvba, jtv, and I agreed that we wanted to get rid of it, so we agreed to
actually get rid of it.
We will be dropping Celery from MAAS this cycle, so hopefully this won't be a problem for long.