curtin fast installer tries to match swap with memory
Bug #1427164 reported by
Jonathan Davies
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
curtin |
Invalid
|
High
|
Unassigned |
Bug Description
Using the curtin fast installer on a box with a significant amount of memory (say: 500G), and curtin tries to match the memory with the swap space.
This caused a compute node with 100G of disk to have 99G of swap space and a 1G / partition.
MAAS version: 1.5.4+bzr2294-
Changed in maas: | |
status: | New → Triaged |
Changed in curtin: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in maas: | |
status: | Triaged → Invalid |
status: | Invalid → Triaged |
importance: | Undecided → High |
Changed in maas: | |
status: | Triaged → Invalid |
Changed in curtin: | |
status: | Incomplete → Invalid |
To post a comment you must log in.
A work around for the moment is to either force the swap off, if you don't want it or set it to a fixed size.
Modifying /etc/maas/ curtin_ userdata add the following to disable
swap: None
to set a fixed size:
swap:
size: 10G
to set a maximum size but still allow the calculation:
swap:
maxsize: 10G