We're updating the issue view to help you get more done. 

change of package size does not change "max_swap" value

Description

Changing a machine to another package leaves the "max_swap" value unchanged. e.g in the below example I changed a machine from a package that uses 8GB of Ram to one that uses 64MB - as you can see from the vmadm get json output the "max_swap" value remains unchanged.

"cpu_shares": 3,
"zfs_io_priority": 5,
"max_physical_memory": 64,
"max_locked_memory": 64,
"max_swap": 8256,
"cpu_cap": 50,
"tmpfs": 64,

Environment

None

Status

Assignee

Heinz N. Gies

Reporter

Mark Slatem

Labels

Fix versions

Affects versions

0.6.0
0.6.1

Priority

High