Allow turning off auto-create-on-allocate for pods
Bug #1706461 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
we have hit a few issues around auto-allocation, even though it's not something we ever want to use. It would be nice if we could just turn it off, per pod. Even if the issues we've hit are fixed, it would be a nice robustness enhancement - an easy way to work around any future issues that might come up.
This is with 2.2.2 (6094-g78d97d0-
| summary: |
- wishlist: allow turning off auto-create-on-allocate for pods + Allow turning off auto-create-on-allocate for pods |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| milestone: | none → 2.3.0 |
| tags: | added: foundations-engine |
| tags: | added: internal |
Revision history for this message
| Jason Hobbs (jason-hobbs) wrote | #1 |
| tags: | removed: foundations-engine |
| Changed in maas: | |
| milestone: | 2.3.0 → next |
| tags: | added: pod |
Revision history for this message
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Won't Fix |
| Changed in maas: | |
| milestone: | next → none |
To post a comment you must log in.
We have no need for this anymore, now that tag constraints prevent auto allocation.