Snapped MAAS backup instructions backup unnecessary items
Bug #2039292 reported by
Chris Johnston
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Undecided
|
Unassigned | ||
| MAAS documentation |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Following the instructions to backup MAAS results in a very large (multi-GB) file. This is due to the instruction of `sudo snap save maas` saving boot-resources and proxy cache. Outside of an offline environment (and possibly not even there), I'm not sure it is needed to backup the boot-resources and proxy cache. In fact, the instructions for backing up a deb based MAAS exclude boot-resources. Without a proper mechanism to avoid unneeded bloat of the backups, is there anything gained by using `snap save` over the method used for deb based MAAS?
| Changed in maas-doc: | |
| importance: | Undecided → Low |
| Changed in maas: | |
| status: | New → Invalid |
| Changed in maas-doc: | |
| status: | New → Invalid |
To post a comment you must log in.
