If no volume_size is defined, the default behavior was to set one to
10GB. However, the proper way to handle this is to use an "Image"
boot source rather than "Volume From Image".
Change-Id: Ib4a33f224ea1044b076d965faa164686da071cc4
Signed-off-by: Eric Ball <eball@linuxfoundation.org>
name: {{ name_prefix }}-{{ labels }}
slaveOptions:
bootSource:
name: {{ name_prefix }}-{{ labels }}
slaveOptions:
bootSource:
- volumeSize: {{ volume_size }}
+{%- if image_type == "volumeFromImage" %}
+ volumeSize: {{ volume_size }}{% endif %}
{%- if hardware_id %}
hardwareId: {{ hardware_id }}{% endif %}
{%- if instance_cap %}
{%- if hardware_id %}
hardwareId: {{ hardware_id }}{% endif %}
{%- if instance_cap %}
# Default volume size of 10
if "volume_size" not in section_all_machines:
# Default volume size of 10
if "volume_size" not in section_all_machines:
- section_all_machines.update(volume_size="10")
+ section_all_machines.update(image_type="image")
+ else:
+ section_all_machines.update(image_type="volumeFromImage")
if "labels" not in section_all_machines:
# "section" is the name of the cloud agent, which is the default label
section_all_machines.update(labels=section)
if "labels" not in section_all_machines:
# "section" is the name of the cloud agent, which is the default label
section_all_machines.update(labels=section)
--- /dev/null
+---
+fixes:
+ - |
+ If no volume_size is defined, the default behavior was to set one to
+ 10GB. However, the proper way to handle this is to use an "Image"
+ boot source rather than "Volume From Image".