yahoo-eng-team team mailing list archive

[Stephen Finucane <1770658@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1934770 ***
    https://bugs.launchpad.net/bugs/1934770

This was fixed in Xena as part of bug #1934770. I have marked this as a
duplicate of same.

** This bug has been marked a duplicate of bug 1934770
   Mismatch between forced host and AZ prevents move operations

-- 
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/1770658

Title:
  availability-zone option needs to validate arguments between zone and
  host

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Description
  ===========
  If I tried to create VM instance with specified availability-zone option with invalid forced-host, I succeed to make VM at invalid compute host.

  I do not know if this is intentional, but it's different from
  intuition since host-aggregate does not have compute host at all. I
  think if admin has any other meaningful properties for the
  availability-zone (e.g. Network binding for the zone), it do make more
  severe problem.

  
  Steps to reproduce
  ==================
  server create --availability-zone Dev:compute01 ....'
  (host-aggregate called 'Dev' do not have host 'compute01') 

  Expected result
  ===============
  Could not make instance

  Actual result
  =============
  Could make instance on host which to be forced.

  Environment
  ===========
  mitaka-eol on upstream. But, seems to be same for master.
  filter-scheduler (+ availability_zone_filter)
   
  2. Which hypervisor did you use?
  libvirt + kvm

  2. Which storage type did you use?
  Ceph

  3. Which networking type did you use?
  Neutron with linux-bridge

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