Low disk can deadlock boot resources synchronisation
Bug #1489380 reported by
Gavin Panella
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
On systems with low disk space the boot-resources synchronisation from
region to cluster can deadlock because old resources are not removed
until new resources are present.
I think we should keep the new-before-old pattern, but MAAS could help
in several ways:
* Tell the user about low disk space, and how it's affecting MAAS.
* Remove /some/ old files and try syncing again.
* Provide a *force* option that removes old files before syncing.
| Changed in maas: | |
| milestone: | none → 2.5.0beta2 |
| Changed in maas: | |
| milestone: | 2.5.0beta2 → 2.5.0rc1 |
| Changed in maas: | |
| milestone: | 2.5.0rc1 → 2.5.x |
Revision history for this message
| Adam Collard (adam-collard) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team