Nova does not respect default_schedule_zone `None`
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Hello,
DESCRIPTION
-----------
I want Nova to behave like that when Availability Zone is not specified (`Any Availability Zone` is set in Horizon), it will create VM in random AZ.
STEPS TO REPRODUCE
------------------
Steps I do to configure that:
1. In `nova.conf` I set `default_
2. I create 2 availability zones (2 host aggregates each with 1 hypervisor added).
3. I try to create VM In Horizon with `Any Availability Zone` and it results in following error:
The requested availability zone is not available (HTTP 400).
The commands I executed to create AZs:
```
openstack aggregate create HA-Test1 --zone AZ-Test1 --property availability_
openstack aggregate create HA-Test2 --zone AZ-Test2 --property availability_
openstack aggregate add host HA-Test1 os-compute-01
openstack aggregate add host HA-Test2 os-compute-02
```
POINT
-----
Now this doesn't work as expected, but(!) when I remove `nova.conf` attribute `default_
Therefore I think that Nova doesn't handle `None` as python `None`, but as string (As if you set default schedule zone to zone `None`).
ENVIRONMENT
-----------
I am using stable Pike release with KVM + Libvirt installed via Openstack-Ansible on Ubuntu 16.04.
[1] https:/
[2] https:/
Changed in nova: | |
status: | New → Confirmed |
assignee: | nobody → Ritesh Paiboina (rsritesh) |
Changed in nova: | |
assignee: | Ritesh Paiboina (rsritesh) → nobody |
IMO, the issue is not an issue of nova.
Probably it is an issue of oslo.config.