get bandwidth limit: improve detecting if storages are involved
Previously, calling with e.g. $storage_list = [undef] would lead to an early return of $override and not consider the limit from datacenter.cfg. Refactoring the bandwidth limit handling for migration introduced calls such as described above, which broke applying the limit from datacenter.cfg for VM RAM/state migration. Reported in the community forum: https://forum.proxmox.com/threads/37920/post-513005 Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
committed by
Thomas Lamprecht
parent
b9e309d667
commit
0227e28e8e
@ -2082,7 +2082,7 @@ sub get_bandwidth_limit {
|
||||
}
|
||||
|
||||
# Apply per-storage limits - if there are storages involved.
|
||||
if (defined($storage_list) && @$storage_list) {
|
||||
if (defined($storage_list) && grep { defined($_) } $storage_list->@*) {
|
||||
my $config = config();
|
||||
|
||||
# The Datastore.Allocate permission allows us to modify the per-storage
|
||||
|
||||
Reference in New Issue
Block a user