Heat fails to create volume if no availability zone provided
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Invalid
|
Medium
|
Unassigned |
Bug Description
All nova/cinder hosts are in non "nova" availability zone, I mean they are in, for example "my_az" availability zone. In such case Heat will fail to deploy nova server with block_device_
Part of template:
resources:
server:
type: OS::Nova::Server
properties:
user_
key_name: { get_param: key_name }
block_
-
image_id: { get_param: image }
flavor: { get_param: flavor }
networks:
- port: { get_resource: server_port }
user_data:
Exact same behavior when booting with block_device_
Request snippet from cinder-
{
'request_spec': {
u 'source_replicaid': None,
u 'volume_
u 'volume_metadata': [],
u 'availability_
u 'reservations': [u '0382a27d-
u 'replication_
u 'snapshot_id': None,
u 'id': u 'e3019d25-
u 'size': 80,
u 'display_name': u '',
u 'source_replicaid': None,
u 'display_
u 'project_id': u 'd877486d3dd24b
u 'metadata': {},
u 'status': u 'creating',
u 'volume_type_id': None,
u 'multiattach': False,
u 'source_volid': None,
u 'qos_specs': None,
u 'consistencygro
u 'user_id': u '11a682025d5dce
u 'attach_status': u 'detached',
u 'cgsnapshot_id': None,
u 'encryption_
},
u 'source_volid': None,
u 'cgsnapshot_id': None,
u 'image_id': u 'ce17b5db-
u 'snapshot_id': None,
u 'consistencygro
u 'volume_type': {},
u 'volume_id': u 'e3019d25-
}
}
As one can see there is u 'availability_
Heat from OpenStack Liberty (Version: 1:5.0.1-
# heat-manage db_version
65
It looks like a Nova issue? Can you make it work with the equivalent nova boot command line call?