'write_dhcp_config' tasks are not executed in order
Bug #1324943 reported by
Raphaël Badin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
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 |
tags: | added: celery |
To post a comment you must log in.
We will be dropping Celery from MAAS this cycle, so hopefully this won't be a problem for long.