zones created via zone import don't have pool attributes
Bug #1690184 reported by
Tim Simmons
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
In Progress
|
Critical
|
Dmitry Galkin | ||
Bug Description
Any zone that is created via zone import will be created with an empty
pool attributes dictionary.
This means that any zone import zone will fall through to whatever default pool
is configured via the pool scheduler.
It would be nice to have some way to specify pool attributes with a zone import,
however, this is difficult as it can't be in the HTTP body, as that's of type text/dns,
and it's the zone data itself.
Perhaps an HTTP header? The api-wg would die, but we can't think of anything better at first glance.
| Changed in designate: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to designate (master) | #1 |
| Changed in designate: | |
| assignee: | nobody → Dmitry Galkin (galkindmitrii) |
| status: | Confirmed → In Progress |
Revision history for this message
| Dmitry Galkin (galkindmitrii) wrote | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on designate (master) | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/