Nova boot does not respect zone name if node is specified
Bug #1495946 reported by
Ilya Shakhat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Raga lahari |
Bug Description
Version DevStack / Liberty (commit-id 9f61d1eb)
Steps to reproduce:
1. Boot new instance specifying non-existing zone name but valid host name:
nova boot --image <image-id> --nic net-id=<net-id> --flavor m1.nano --availability-zone foo:devstack my_vm
2. nova show my_vm shows that the instance was started in availability zone "nova".
It's expected that Nova rejects to boot instance within wrong zone, but it uses only hostname part of it.
Changed in nova: | |
assignee: | nobody → Raga lahari (raga-lahari) |
tags: |
added: scheduler removed: availability-zones spawn |
To post a comment you must log in.
I'm tagging it with "api" because I assume that this should be checked on that level with an appropriate return code.