When a custom image is updated it shows as synced before copied to rack controllers
Bug #2003980 reported by
Jorge Merlino
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
3.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
3.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
3.2 |
Invalid
|
High
|
Unassigned | ||
3.3 |
Invalid
|
High
|
Unassigned | ||
3.4 |
Invalid
|
High
|
Unassigned |
Bug Description
When a custom image is loaded to MAAS it is shown in the web page that it is downloading, then it is shown as "Syncing to rack controllers" and lastly is shown as "Synced".
When the same image is updated (uploaded again with the same name) it is shown that it is being downloaded but immediately after that it shows as "Synced", before the rack controllers have been able to update it.
In this last state it is possible to launch a machine that will use the old version of the image even if the web page is showing the new version as "Synced".
Changed in maas: | |
status: | New → In Progress |
assignee: | nobody → Jorge Merlino (jorge-merlino) |
Changed in maas: | |
milestone: | none → 3.4.0 |
importance: | Undecided → Low |
Changed in maas: | |
status: | Incomplete → Triaged |
assignee: | nobody → Igor Brovtsin (igor-brovtsin) |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.5.0 → 3.5.0-beta1 |
Changed in maas: | |
milestone: | 3.5.0-beta1 → none |
To post a comment you must log in.
MAAS bug-council,
This fix is desired on MAAS 3.0.
Once (and if) the MR to 3.4 is approved/merged, can we send backport MRs to 3.3/3.2? (And we'd follow with 3.1/3.0 as well, maintained by SEG.)
Thanks!