availability-zone option needs to validate arguments between zone and host
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
Medium
|
Yang Youseok | ||
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_
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
| daixianmeng (daixianmeng) wrote | #1 |
| Yang Youseok (ileixe) wrote | #2 |
| Changed in nova: | |
| assignee: | nobody → Yang Youseok (ileixe) |
| tags: | added: scheduler |
| Balazs Gibizer (balazs-gibizer) wrote | #3 |
| Changed in nova: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Balazs Gibizer (balazs-gibizer) wrote | #4 |
This may be a bug. You can modify this logic check.(add aggregat and host check)