yahoo-eng-team team mailing list archive

[Ilya Shakhat <ishakhat@xxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1495946

Title:
  Nova boot does not respect zone name if node is specified

Status in OpenStack Compute (nova):
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1495946/+subscriptions