Invalid availability zone name with ':' is accepted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Tetsuro Nakamura | ||
| Ocata |
Fix Committed
|
Medium
|
Matt Riedemann | ||
| Pike |
Fix Committed
|
Medium
|
Matt Riedemann | ||
Bug Description
According to the parse_availabil
1. An admin creates a host aggregate with availability_zone = bad:name:example
2. An admin tries to create a server with availability_zone = bad:name:example
3. The nova-api parse the request and split the availability_zone value with ':'
4. Then it recognizes az=bad, host=name, node=example
5. Nova returns 'No valid host found' because there is no availability zone whose name is 'bad'.
To solve this problem following fixes are needed:
Option A:
* Do not allow admins to create a host aggregate whose availability_zone name including ':'.
* Document this specification.
Option B:
* Deprecate the legacy admin hack which uses az:host:node and allow ':' for az name.
| summary: |
- Invalid availability zone name can be accepted + Invalid availability zone name with ':' is accepted |
| Changed in nova: | |
| status: | New → Confirmed |
| tags: | added: api |
| Changed in nova: | |
| assignee: | nobody → Tetsuro Nakamura (tetsuro0907) |
| Changed in nova: | |
| importance: | Undecided → Medium |
| Changed in nova: | |
| assignee: | Viktor Varga (vvargaszte) → Tetsuro Nakamura (tetsuro0907) |
| no longer affects: | nova/ocata |
| Changed in nova: | |
| assignee: | Tetsuro Nakamura (tetsuro0907) → Matt Riedemann (mriedem) |
| Changed in nova: | |
| assignee: | Matt Riedemann (mriedem) → Tetsuro Nakamura (tetsuro0907) |

I can reproduce it in nova master (commit 3ce0a050e1e611a d87336406c18952 2ee63ded30) .