All auto-allocated VMs go to the first pod
Bug #1706459 reported by
Jason Hobbs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We have 3 pods setup in our MAAS. When an allocate request comes in with constraints that don't match any existing machines, MAAS allocates a new VM from a pod. It always picks the first pod, which causes its resources to be exhausted quickly while the other pods still have free resources. Here's the output from 'pods read':
http://
You can see that pod 2 has available resources, while pod 1 has negative resources.
This is with 2.2.2 (6094-g78d97d0-
tags: | added: pod |
To post a comment you must log in.
MAAS does not have a scheduling algorithm to balance resource allocation between pods. However, you can select which pod you want your resources created. The issue here is that it keeps allocating when resources are not available.
https:/ /bugs.launchpad .net/maas/ +bug/1706458