Correct availability_zone to be non-mandatory in heat
As per CLI and GUI, availability_zone is not mandatory. In templates,
it is. This is incorrect.
This patch corrects behaviour to match CLI and GUI.
Change-Id: Ice37340f084ea65bd4b46562145e82ede6bc0df5
Story: 2006586
(cherry picked from commit 2799a5fcd7
)
This commit is contained in:
parent
b6822c2633
commit
0a8949397b
|
@ -56,7 +56,6 @@ class HostAggregate(resource.Resource):
|
||||||
AVAILABILITY_ZONE: properties.Schema(
|
AVAILABILITY_ZONE: properties.Schema(
|
||||||
properties.Schema.STRING,
|
properties.Schema.STRING,
|
||||||
_('Name for the availability zone.'),
|
_('Name for the availability zone.'),
|
||||||
required=True,
|
|
||||||
update_allowed=True,
|
update_allowed=True,
|
||||||
),
|
),
|
||||||
HOSTS: properties.Schema(
|
HOSTS: properties.Schema(
|
||||||
|
|
|
@ -0,0 +1,8 @@
|
||||||
|
---
|
||||||
|
fixes:
|
||||||
|
- |
|
||||||
|
Erroneously, availability_zone for host aggregate resource types was
|
||||||
|
considered mandatory in heat templates.
|
||||||
|
|
||||||
|
Behaviour has been adjusted to bring this in line with the CLI and GUI, in
|
||||||
|
which it is optional.
|
Loading…
Reference in New Issue