yahoo-eng-team team mailing list archive

[Yang Youseok <1770658@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

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

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

Status in OpenStack Compute (nova):
  New

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